On 17/8/00 12:11 pm, David Bovill <[EMAIL PROTECTED]> wrote:
> How can you tell when you have made changes to the stack in memory and
> therefore need to save it when it is closed. Do you have to tracke every
> change? The save command seems to save even when you have done nothing -
> right.
>
> Can you do something fancy like an MD5digest of the stack in memory??? The
> issue is that it takes a long time to save a database stack as it gets large,
> and I don't want to loose data. What's the best strategy?
You have to track the messages you get when a stack is altered: things like
closeField, mouseDown (with pointer tool), etc. It can be fairly tricky to
ensure you catch everything - but if you know what actions your users are
allowed to take (e.g. in a database entry and deletion of text could be
covered by closeField) it should be possible to do without too much trouble.
Regards,
Kevin
Kevin Miller <[EMAIL PROTECTED]> <http://www.runrev.com/>
Runtime Revolution Limited (formerly Cross Worlds Computing).
Tel: +44 (0)131 672 2909. Fax: +44 (0)1639 830 707.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
