🚀 go-pugleaf

russell@acf3.NYU.EDU (Bill Russell) writes:
>
>Yes, indeed.  The stack backup problem kills me -- it makes a brilliant
>utility like DiskFit into a painful-to-use chore.  Even though we all know
>why the problem occurs -- it should be considered a BUG.  It is a great pitty
>that Atkinson thinks that saving is something the lowbrow user can NEVER be
>taught to do.  So we all have to suffer.

Sometimes scripts in cards need to alter the state of the stack.  For
instance, info buttons often change the state of a field to visible.
Since a user may alter the states of several cards, even at the browse
level, or he may leave the stack and then come back to it, this state
information has to be stored in the stack file unless you introduce some
rather complex linked files which personalize a stack for each user.

I agree that HC modifies to often.  It will usually time-stamp stacks
for which there is no changed state information, although sometimes
it will leave the dates alone.  Remove all the scripts from the Slide
Show and it still time-stamps when you visit; look at the index to the
recently posted Periodic Table and it doesn't.  Can anybody figure out
why?

------------------------------------------------------------------------------
Oliver Steele				  ...!{decvax,ihnp4}!mcnc!unc!steele
							steele%unc@mcnc.org

	"If God had meant for man to Walk, he would have given us Feet."