Peter Alcibiades wrote: > What seems to happen, single number of times a year on a stack > in daily use, is that quitting produces an abortive save. The > stack script calls for save this stack on close. The stack > itself is not corrupted, it is saved as eg stack.rev~.
Your handling of that sounds good, but I'm curious: have you pinned down what's causing these saves to be interrupted?
-- Richard Gaskin Managing Editor, revJournal _______________________________________________________ Rev tips, tutorials and more: http://www.revJournal.com _______________________________________________ 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
