Le 15 avr. 07 à 18:11 Soir, Lennox Jacob a écrit: > I have done it with encoding/decoding and I have used file.locked > to save the file in a locked state so that its contents cannot be > altered unless unlocked, and hopefully the file cannot become > corrupted, again unless if unlocked.
Well, I think you should not do that. It's probably written in the Apple Interface Guidelines or so, but if the user didn't wanted (or does not know) that the file is locked as soon as it is created, he will be annoyed when he moves the file to the trash and empties it. At least, I would. In my opinion, I would simply use EncodeBase64, revers the resulting string (like "abcd" becomes "dcba") and then changing the ascii value of every character to the inverted one (ascii 0 becomes ascii 255). Writing to a binary file, not a text file, of course. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
