What happens if you: set the destroyStack of stack origStack to true close stack origStack wait for messages -- to assure that the mem-resident copy was destroyed delete file origStack save stack newerStack as origStack delete file newerStack
?? Phil ----- Original Message ----- From: "Shari" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 11, 2002 4:57 PM Subject: Save stack as... > The goal: > > To replace a stack that exists, with a newer version of the same stack. > > The full filepaths to the stacks are in the variables, and the stacks > are in different directories. > > delete file origStack > save stack newerStack as origStack > delete file newerStack > > This prompts the "a stack exists, do you want to purge or save" > dialog. Even though the stacks were all originally closed. How do I > bypass the dialog? I don't want to open the stacks. I simply want > to replace file origStack with file newerStack, deleting the unneeded > copies. And do this behind the scenes. > > Anybody? > > > -- > --Shareware Games for the Mac-- > http://www.gypsyware.com > _______________________________________________ > metacard mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/metacard _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard