Hi Bill,
Actually, if you duplicate the file on disk, you'll not get a copy of
the current stack 'they are working on' (as you say) but a copy of
the stack as it was last saved.
So you might prefer to clone the stack and save this clone.
BTW it's not an easy process (above all when the main stack has
substacks) since Rev does not accept to have two stacks with the same
name in memory.
So you have to rename temporarily all stacks to save a real clone
(all stacks names included and not 'copy of')
Probably the 'SaveProjects' handler in the card of my 'Backups
Picker' plugin might get you started to achieve this.
Best Regards from Paris,
Eric Chatonet
Le 20 févr. 07 à 07:49, Bill Vlahos a écrit :
I want to be able to have the user easily make a copy of the stack
they are working on as a way to backup the stack. This would be
something like "Save a Copy".
However, I don't want to change the active path of the stack. I
still want the stack they are working on to stay put and be the
working stack.
The following button script doesn't work and gives this error
Chunk: source is not a container
on mouseUp
answer folder "Select destination folder for backup: "
if it is not "Cancel" then
revCopyFile this stack, it
end if
end mouseUp
How can I make this work?
Bill Vlahos
------------------------------------------------------------------------
----------------------
http://www.sosmartsoftware.com/ [EMAIL PROTECTED]/
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
