Program Testing and Persistent Properties
Bob Warren
warren at howsoft.com
Sun Aug 8 03:33:22 EDT 2004
----- Original Message -----
From: "Ken Ray" <kray at sonsothunder.com>
To: "Bob Warren" <warren at howsoft.com>; "Use Revolution List"
<use-revolution at lists.runrev.com>
Sent: Sunday, August 08, 2004 3:04 AM
Subject: Re: Program Testing and Persistent Properties
> > When the option is selected: <<<<<<<<<<<<<<<<<<<<<<<<<<<
> > 1. On selecting the Browse Tool (Run scripts and interact), save the
> > stack to the HD temporarily.
> > 2. On selecting the Pointer Tool (edit), substitute the modified stack
with
> > the temp stack.
> >
> > Things are easy to say, but more difficult to do. Do you think that
> > something along these lines would be viable?
>
> Not to throw water on your suggestion, but no, I don't think it would be
> viable (at least not as a permanent change to Rev), and here's the
reason...
> the substituting of a stack with another stack would be disconcerting (to
> say the least) to experienced Rev developers. The reason is that they (and
> I) are too used to just being able to switch to browse tool to try
something
> out. We are *empowered* by the single mode, rather than hampered.
So whoever doesn't want it simply doesn't turn on the option..........
What I was suggesting was a permanent optional choice, not a permanent
change to a fixed mode that experienced users would not like.
(Sorry to have called you "Ray", it was a slip of my typewriter.)
More information about the use-livecode
mailing list