Understanding 'the defaultStack'

[Peter M. Brigham]

I have a stack that in one place and one place only when the script calls for “ask … with … as sheet” sheets the ask dialog and then it promptly loses focus. If I try to type a replacement for the default text or hit <return> to affirm the default text, nothing happens — the dialog has lost focus as one can see by the hilite color for the text and the lack of blue background for the “OK” button. I have to click in the text field, then do what I want with the dialog. Have not tracked this down. At this point I can’t recall which “ask…” command this occurs in so I can post that section of script, but it only happens in that one place. I don’t know if this is related to the defaultstack issue.

— Peter

Peter M. Brigham
pmbrig at gmail.com


> On Oct 8, 2016, at 4:54 PM, J. Landman Gay <jacque at hyperactivesw.com> wrote:
> 
> On 10/8/16 3:22 PM, Richard Gaskin wrote:
>> The rule Dr. Raney gave me is that the defaultStack is the topmost
>> visible stack of the lowest mode.
> 
> 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.e.:
> 
> Stack One
> visible
> topstack
> mode 1
> 
> 
> command: go stack stackTwo
> 
> stackTwo
> visibility false
> mode 1
> 
> command: put the defaultstack
> -> stackTwo
> 
> 
> So...?
> 
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.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