>From: Dave Cragg <[EMAIL PROTECTED]>
>If you don't want to mess around with the development environment,
>another approach is to make a "utility stack" for each project you
>are working on. You can add buttons to these stacks that perform
>frequently used operations. (Anything you find yourself t
At 9:53 AM -0600 5/4/00, Scott Raney wrote:
>> Whats neededis a "global static" mode.
>
>The solution is much simpler: just lock messages before you go to the
>card. For example running "lock messages; go next" in the message box
>will do what you want. Tuv Snyder told me he even put a button i
On Wed, 3 May 2000, Sivakatirswami wrote:
> From: Scott Raney <[EMAIL PROTECTED]>
> > Subject: Re: Lock Messages "Permanently"
>
> > On Tue, 2 May 2000, Sivakatirswami wrote:
> >
> >> There are times when I want "all scripts to shut do
On Tue, 2 May 2000, Sivakatirswami wrote:
> There are times when I want "all scripts to shut down" while I do basic
> construction. But lockMessages set to true only "sticks once" i.e. if you
> are in the stack components examining various cards and work to create new
> card in new positions add
