Chipp, (sorry about the name. I said I'm having vision problems, smile)
Thanks, I was beginning to come to the same conclusion; which seems
to indicate that in order for any application to be able to Save
anything, it must create documents apart from itself that are then
used to load up when needed. This is going to require a change in
strategy on my part or the used of stacks with the stackrunner in
lieu of stand alones, which is not as pretty but acceptable I suppose.
Would have gotten back sooner on this but turned in early last night
and got a late start today.
Joe Wilkins
On Apr 22, 2007, at 11:50 PM, Chipp Walters wrote:
Joe,
(It's Chipp with 2 p's)
First of all, you can't save data in a standalone. I assume you
already know this. You need to store your data in a stack or file
OUTSIDE the standalone.
If what you're after is the 'Save As..' dialog, read up on "ask file".
There are two parts to Save As. The first part is asking the user for
the pathname to save the file to. The second part is actually doing
the save.
Create a button:
on mouseUp
ask file "Choose a place to save your stack"
if the result is "cancel" or it is empty then exit to top
put it into tPathname
save stack "JoesStack" as tPathname
end mouseUP
This will save the stack "JoesStack" to the file specified.
-Chipp
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
