defaultStack Scope

Ken Ray kray at sonsothunder.com
Fri Jul 12 07:31:01 EDT 2002


Dan,

The defaultStack is changed whenever a new stack is opened, so if you do
this:

on mouseUp
   set the defaultStack to "A"
   -- defaultStack is "A"
   open inv stack "B"
   -- defaultStack is now "B", even though A still appears (UI-wise) to be
the current stack
   -- To reset the focus, call it again:
   set the defaultStack to "A"
end mouseUp

You can see how the focus shifts from one to the other. SuperCard had a
similar property called "topWindow" that did the same thing.

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/


----- Original Message -----
From: "Dan Shafer" <dan at danshafer.com>
To: <use-revolution at lists.runrev.com>
Sent: Friday, July 12, 2002 2:13 AM
Subject: defaultStack Scope


> It appears that setting the defaultStack of a stack file is a
> temporary action. If I change it from the Message Box, e.g., it never
> "sticks." If I say:
>
> set the defaultStack to "Foo"
>
> and then
>
> put the defaultStack
>
> it always returns the stack that was the default before I typed the
message.
>
> I can put the same two commands in a button's mouseUp handler and it
works.
>
> So the question is what else can reset the defaultStack property
> without my doing so explicitly?
> --
> -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
> Dan Shafer
> Technology Visionary - Technology Assessment - Documentation
> "Looking at technology from every angle"
> http://www.danshafer.com
> 831-392-1127 Voice - 831-401-2531 Fax
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the Use-livecode mailing list