Richard Gaskin wrote:
>
>
> Corruption of a stack file per se is very rare with Rev
>
>
Yes, and strictly speaking this is not what is happening. 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~. But the file stack.rev which is created by the save is corrupt
and cannot be launched by the splash. The only solution seems to be to test
for the existence of the ~ file in the splash stack. If found, delete the
stack.rev file, rename stack.rev~ to stack.rev. And pray you haven't failed
to think of something else!
Peter
--
View this message in context:
http://www.nabble.com/quick-question-about-splash-stacks-tp18686349p18706767.html
Sent from the Revolution - User mailing list archive at Nabble.com.
_______________________________________________
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
