classic file paths

Jeffrey Reynolds jeff at
Fri Sep 2 14:31:46 EDT 2005

Thanks, I have been doing this and the structure under classic is what 
i thought it was


the problem is if i get the file path (using answer file) with an macos 
app running on osx under classic, this file path will not work (ie 
setting the filename of a image object). works great in osx, just 
classic not working with rev 251 engines. The only thing i could think 
of was that there was something different in setting a filename path in 
classic than what you get when you request it with answer file or long 
stack name, etc.



On Sep 2, 2005, at 1:00 PM, use-revolution-request at 

> At 3:03 AM -0400 9/1/2005, Jeffrey Reynolds wrote:
>> I guess its a bit moot since i will be having an osx version, so
>> wont have to have an macos running under classic, but I would like
>> to know the file path structure is for my own edification.
> There's some variation between OS X and Classic, but the easiest way
> to explore this is to put this in the message box:
>    answer file "What file?";answer it
> This lets you pick a file, then shows you what the path to the file
> looks like. Helpful when debugging, or just to generally investigate
> what different file paths look like.
> -- 
> jeanne a. e. devoto ~ revolution at

More information about the Use-livecode mailing list