Thanks for the reply,
Sorry, yes it is OS X ...
In fact, I have not used close, and I have used nil since April 14,
and the problem could be the Spotlight, but now also today i get an
report that the user get my error message twice in an 3 minutes, when
he should Save a file, the same file. And this time the user have
"turned off" Spotlight in the System Preferences. He also said that
he get the error message before, but not so often.
The mostly other reports is just "one time reports", so I thought it
could be Spotlight.
Regards,
Sven E
On 2007-05-03, at 20:43, Charles Yeomans wrote:
>
> On May 3, 2007, at 2:01 PM, Sven E Olsson wrote:
>
>>
>> if I have a code like this:
>>
>> f = GetFolderitem("myfile.txt")
>> WriteToFile = f.CreateAsTextFile <<<<---------------- is the file
>> locked now for other apps (in use by my self)?
>
> Maybe, maybe not. Assuming that you're talking about Mac OS X, it
> depends on how RS has implemented this method.
>
>
>>
>> if WriteToFile <> nil then
>> WriteToFile.WriteLine("Hello")
>> WriteToFile.close <<<<---------------------- is the file unlocked now
>
> Don't use Close. Set the TextOutputStream object to nil. There are
> all sorts of reasons why this is the way that you should do it.
>
> Charles Yeomans
> _______________________________________________
>
Sven E
-----------------------
REALbasic 2007R2 OS X 10.4.9 Intel and 10.4.9 PPC
SEEdit Maxi THE XHTML EDITOR FOR MACINTOSH
http://www.seedit.info
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
