Understanding 'the defaultStack'

[J. Landman Gay]

That's what I saw too in my experiment, but I was issuing commands from the 
message box. When Graham did a "go stack invisibleStack" the defaultstack 
didn't change to it.

>From what Monte said, I'm guessing that Graham's running script was in the 
original stack and maybe the engine hadn't done its swap yet.

--
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com



On October 8, 2016 6:17:48 PM "Jeanne A. E. DeVoto" 
<revolution at jaedworks.com> wrote:

> At 3:54 PM -0500 10/8/2016, J. Landman Gay wrote:
>>I thought visibility might impact it (I believe that's the case with
>>Graham's stack) so I did some quick tests and even though there was
>>a visible mode-1 topstack, going to the invisible one did change the
>>defaultstack. Thus, my curiosity.
>
>
> I quote:  "The topStack is the frontmost stack with the lowest mode."
>
> The mode runs from 0 to 13 (unless someone's added some modes
> lately), and invisible isn't one of the modes-a toplevel visible
> stack has the same mode as a toplevel invisible one.
>
> (I don't claim this makes actual sense, mind you....)
> --
> jeanne a. e. devoto
> livecode at jaedworks.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode