Some Basic Misunderstandings/Problems with RunRev

[Björnke von Gierke]

How to save stacks using RunRev standalones:
Normally one can save a stack using the "save" command. But standalones 
generated with RunRev can't save themselves. That means that every 
stack within the application is unable to save itself. So one has to 
save a stack that is not part of the Application. Many developer use a 
so called "Splash screen" approach. The application itself is only a 
splash screen, which then loads all the other stacks from a predefined 
location.  For example like this:

on startup
   hide me
   go stack "Interface.rev"
end startup

for this to work the stack "Interface.rev" just has to be in the same 
directory as the application. As "Interface.rev" is not part of the 
application file, it can be saved without problem. As long as it is not 
on a CD or a write protected location as the application folder of Win 
XP, but that is another problem.