Le 28 avr. 08 à 22:34 (soir), Harrie Westphal a écrit:
> Is there a logical reason why REALbasic sets FolderItem.LastErrorCode
> to 101 when you delete a file? Watching the events in the debugger
> you can see that the file exists, has been read in and it shows the
> f.exists=true, f.LastErrorCode=0. Now when f.delete is executed
> f.exists goes to false, which I would expect, but f.LastErrorCode
> goes to 101, which seems odd. Yes, the file no longer exists which is
> what 101 is telling you, but it existed at the point in time when the
> f.delete was executed so why throw a 101 error at that time? I guess
> you could argue that that is verification that the file was deleted,
> but f.exists going to false would also tell you that. Just seems odd
> to me.
I've tracked this strange behaviour: if you check in the debugger,
"LastErrorCode" is indeed 101 but if you put MsgBox str
(f.LastErrorCode), you get "0" which apparently means that this is a
mistake in the debugger (like because RB is refreshing the properties
of the folderitem, or something like that).
I'd suggest to file a bug feedback, but with recent changes to this
system, I can't be sure if it's a good thing now.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|