H Jeanne,
At 12:50 AM +0200 5/18/05, Malte Brill wrote:
> JAED> If it's not the main stack of the running application, you canJAED> download the file, replacing the outdated file, then use the revert> JAED> command to load the new version from disk.
Could there be trouble with file permissions? E.g. If the stack is inside the bundle on OsX?
There shouldn't be. The revert command just reads the file - and the application had to do the same thing when it started up. If there's a problem with read permissions for the file, it will exist every time the user runs the application, even without downloading a new copy.
i am sure Malte meant eventual problem with WRITE permissions inside an OS X bundle.
What about that?
Anyway, i would recommend to store stack that might be replaced/ updated into some
other place like where you DO have write permissions:
##Mac OS X/OS 9
specialfolderpath("preferences")
##Prefs folder of current user##Mac OS X:
specialfolderpath("asup")
##Application Support##Win 2000/XP specialfolderpath(35) ##Don't know the english name of this folder, sorry...
##Win 95,96,97,98
specialfolderpath("system")
##a.k.a the black hole: "C:\Windows" :-)##Unix/Linux $HOME ##(Homefolder of current user)
-- jeanne a. e. devoto ~ [EMAIL PROTECTED] http://www.jaedworks.com
Regards
Klaus Major [EMAIL PROTECTED] http://www.major-k.de
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
