One quick question

[Sarah]

The stack will import OK but you will have to add a save button/menu or 
an auto-save feature of some kind. If you want to make a standalone, the 
splash screen method is probably the easiest method, so your original HC 
stack can still be the main data storage and get saved but the engine is 
in a non-writable application file with a splash screen.

Sarah


On Monday, July 15, 2002, at 08:40  AM, Ken Norris (dialup) wrote:

> Hello Rev list,
>
> This is probably covered elsewhere, but I can't read the docs on this 
> laptop
> (it runs out of memory when they open, at the moment) and the subject of
> programming standards compliance came up over at the HC list:
>
> Most classic HC recipe-type db stacks almost always allow text field
> updates, new cards, deleting of old cards, etc., auto-saved back to the
> standalone (because it contains a player in it).
>
> What happens if one tries to convert such a stack to Rev, or even 
> rewrite it
> as a Rev standalone?
>
> Best regards,
> Ken N.
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>