Re: Long Standing Issue with the defaultStack
The stack style is important, its mode influences which stack is toplevel and default. A palette shouldn't be the default stack unless you focus on it, for instance. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On April 18, 2020 4:14:27 PM Bob Sneidar via use-livecode wrote: The only reliable way to change either by script is by setting the style of a stack to “topLevel”. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
Go and Open are synonyms. Bob S > On Apr 18, 2020, at 2:19 PM, Bob Sneidar wrote: > > same thing > > Bob S > > >> On Apr 18, 2020, at 2:18 PM, J. Landman Gay via use-livecode >> wrote: >> >> What do you get if you use "go" instead of "open"? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
https://quality.livecode.com/show_bug.cgi?id=22691 if anyone is interested. Very simple test stacks included. Bob S > On Apr 18, 2020, at 2:20 PM, Bob Sneidar via use-livecode > wrote: > > I’m putting together a simple demo and will post on bulgiest in a few. > > Bob S > > >> On Apr 18, 2020, at 2:18 PM, J. Landman Gay via use-livecode >> wrote: >> >> What do you get if you use "go" instead of "open"? >> >> On 4/18/20 3:48 PM, Bob Sneidar via use-livecode wrote: >>> Okay I created a simple stack with one sub stack. In the card script of >>> stack 1 I put the handler: >>> on openStack >>> put the defaultStack & cr into msg >>> open stack "untitled 2" >>> put the defaultStack & cr after msg >>> open me >>> put the defaultStack & cr after msg >>> end openStack >>> I get: >>> stack "Untitled 1" >>> stack "Untitled 2" >>> stack "Untitled 2” >>> It seems going,opening a stack sets the opened stack to the default… IF >>> IT’s NOT ALREADY OPENED! If it IS, well then you are on your own. The >>> defaultStack is the last stack opened. (I’m assuming it’s a normal stack >>> and not a pallet or something else). >>> Now you would think at this point you can use topStack instead, but NAY! >>> This script: >>> on openStack >>> put the defaultStack && the short name of the topStack & cr into msg >>> open stack "untitled 2" >>> put the defaultStack && the short name of the topStack & cr after msg >>> go me >>> put the defaultStack && the short name of the topStack & cr after msg >>> end openStack >>> produces: >>> stack "Untitled 1" Untitled 1 >>> stack "Untitled 2" Untitled 2 >>> stack "Untitled 2" Untitled 2 >>> After I go me, neither the defaultStack nor the topStack changes! What is >>> more, the untitled 2 stack still has focus!! >>> Just to be certain I disabled all my plugins and relaunched, same thing. >>> This CANNOT BE RIGHT! And if it is the expected behavior, it ought not be. >>> Bob S On Apr 18, 2020, at 12:56 PM, Mark Wieder via use-livecode wrote: On 4/18/20 11:33 AM, Bob Sneidar via use-livecode wrote: > Until I can figure out what is causing it, I cannot trust the > defaultStack. I think the basic lesson here is "if you're going to rely on the defaultstack you should set the defaultstack". -- Mark Wieder ahsoftw...@gmail.com >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> -- >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> HyperActive Software | http://www.hyperactivesw.com >> >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
I’m putting together a simple demo and will post on bulgiest in a few. Bob S > On Apr 18, 2020, at 2:18 PM, J. Landman Gay via use-livecode > wrote: > > What do you get if you use "go" instead of "open"? > > On 4/18/20 3:48 PM, Bob Sneidar via use-livecode wrote: >> Okay I created a simple stack with one sub stack. In the card script of >> stack 1 I put the handler: >> on openStack >>put the defaultStack & cr into msg >>open stack "untitled 2" >>put the defaultStack & cr after msg >>open me >>put the defaultStack & cr after msg >> end openStack >> I get: >> stack "Untitled 1" >> stack "Untitled 2" >> stack "Untitled 2” >> It seems going,opening a stack sets the opened stack to the default… IF IT’s >> NOT ALREADY OPENED! If it IS, well then you are on your own. The >> defaultStack is the last stack opened. (I’m assuming it’s a normal stack and >> not a pallet or something else). >> Now you would think at this point you can use topStack instead, but NAY! >> This script: >> on openStack >>put the defaultStack && the short name of the topStack & cr into msg >>open stack "untitled 2" >>put the defaultStack && the short name of the topStack & cr after msg >>go me >>put the defaultStack && the short name of the topStack & cr after msg >> end openStack >> produces: >> stack "Untitled 1" Untitled 1 >> stack "Untitled 2" Untitled 2 >> stack "Untitled 2" Untitled 2 >> After I go me, neither the defaultStack nor the topStack changes! What is >> more, the untitled 2 stack still has focus!! >> Just to be certain I disabled all my plugins and relaunched, same thing. >> This CANNOT BE RIGHT! And if it is the expected behavior, it ought not be. >> Bob S >>> On Apr 18, 2020, at 12:56 PM, Mark Wieder via use-livecode >>> wrote: >>> >>> On 4/18/20 11:33 AM, Bob Sneidar via use-livecode wrote: >>> Until I can figure out what is causing it, I cannot trust the defaultStack. >>> >>> I think the basic lesson here is "if you're going to rely on the >>> defaultstack you should set the defaultstack". >>> >>> -- >>> Mark Wieder >>> ahsoftw...@gmail.com >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
same thing Bob S > On Apr 18, 2020, at 2:18 PM, J. Landman Gay via use-livecode > wrote: > > What do you get if you use "go" instead of "open"? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
What do you get if you use "go" instead of "open"? On 4/18/20 3:48 PM, Bob Sneidar via use-livecode wrote: Okay I created a simple stack with one sub stack. In the card script of stack 1 I put the handler: on openStack put the defaultStack & cr into msg open stack "untitled 2" put the defaultStack & cr after msg open me put the defaultStack & cr after msg end openStack I get: stack "Untitled 1" stack "Untitled 2" stack "Untitled 2” It seems going,opening a stack sets the opened stack to the default… IF IT’s NOT ALREADY OPENED! If it IS, well then you are on your own. The defaultStack is the last stack opened. (I’m assuming it’s a normal stack and not a pallet or something else). Now you would think at this point you can use topStack instead, but NAY! This script: on openStack put the defaultStack && the short name of the topStack & cr into msg open stack "untitled 2" put the defaultStack && the short name of the topStack & cr after msg go me put the defaultStack && the short name of the topStack & cr after msg end openStack produces: stack "Untitled 1" Untitled 1 stack "Untitled 2" Untitled 2 stack "Untitled 2" Untitled 2 After I go me, neither the defaultStack nor the topStack changes! What is more, the untitled 2 stack still has focus!! Just to be certain I disabled all my plugins and relaunched, same thing. This CANNOT BE RIGHT! And if it is the expected behavior, it ought not be. Bob S On Apr 18, 2020, at 12:56 PM, Mark Wieder via use-livecode wrote: On 4/18/20 11:33 AM, Bob Sneidar via use-livecode wrote: Until I can figure out what is causing it, I cannot trust the defaultStack. I think the basic lesson here is "if you're going to rely on the defaultstack you should set the defaultstack". -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
What is worse, after THIS script runs: on openStack put the defaultStack && the short name of the topStack & cr into msg go stack "untitled 2" put the defaultStack && the short name of the topStack & cr after msg go the owner of me set the defaultStack to the owner of me put the defaultStack && the short name of the topStack & cr after msg end openStack I get: stack "Untitled 1" Untitled 1 stack "Untitled 2" Untitled 2 stack "Untitled 1" Untitled 2 Here, the defaultStack is set by script to stack “Untitled 1” as you would expect, but upon termination of the script, the command "put the defaultStack” reveals that stack “Untitled 2” has reverted to the defaultStack! In other words, going to another stack, or card of a stack by script DOES NOT ALTER the defaultStack, and neither does setting it by script once the script terminates. Additionally it does not make it the topStack. If a user CLICKS in an open stack THEN it becomes the defaultStack AND the topStack. It just does not work by script. The only reliable way to change either by script is by setting the style of a stack to “topLevel”. Bob S > On Apr 18, 2020, at 1:48 PM, Bob Sneidar via use-livecode > wrote: > > Okay I created a simple stack with one sub stack. In the card script of stack > 1 I put the handler: > > on openStack > put the defaultStack & cr into msg > open stack "untitled 2" > put the defaultStack & cr after msg > open me > put the defaultStack & cr after msg > end openStack > > I get: > stack "Untitled 1" > stack "Untitled 2" > stack "Untitled 2” > > It seems going,opening a stack sets the opened stack to the default… IF IT’s > NOT ALREADY OPENED! If it IS, well then you are on your own. The defaultStack > is the last stack opened. (I’m assuming it’s a normal stack and not a pallet > or something else). > > Now you would think at this point you can use topStack instead, but NAY! This > script: > > on openStack > put the defaultStack && the short name of the topStack & cr into msg > open stack "untitled 2" > put the defaultStack && the short name of the topStack & cr after msg > go me > put the defaultStack && the short name of the topStack & cr after msg > end openStack > > produces: > stack "Untitled 1" Untitled 1 > stack "Untitled 2" Untitled 2 > stack "Untitled 2" Untitled 2 > > After I go me, neither the defaultStack nor the topStack changes! What is > more, the untitled 2 stack still has focus!! > > Just to be certain I disabled all my plugins and relaunched, same thing. > > This CANNOT BE RIGHT! And if it is the expected behavior, it ought not be. > > Bob S > > > >> On Apr 18, 2020, at 12:56 PM, Mark Wieder via use-livecode >> wrote: >> >> On 4/18/20 11:33 AM, Bob Sneidar via use-livecode wrote: >> >>> Until I can figure out what is causing it, I cannot trust the defaultStack. >> >> I think the basic lesson here is "if you're going to rely on the >> defaultstack you should set the defaultstack". >> >> -- >> Mark Wieder >> ahsoftw...@gmail.com > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
By the way, this has NOTHING to do with substacks as I initially thought. The same thing happens with separate stacks. > On Apr 18, 2020, at 1:48 PM, Bob Sneidar via use-livecode > wrote: > > Okay I created a simple stack with one sub stack. In the card script of stack > 1 I put the handler: > > on openStack > put the defaultStack & cr into msg > open stack "untitled 2" > put the defaultStack & cr after msg > open me > put the defaultStack & cr after msg > end openStack > > I get: > stack "Untitled 1" > stack "Untitled 2" > stack "Untitled 2” > > It seems going,opening a stack sets the opened stack to the default… IF IT’s > NOT ALREADY OPENED! If it IS, well then you are on your own. The defaultStack > is the last stack opened. (I’m assuming it’s a normal stack and not a pallet > or something else). > > Now you would think at this point you can use topStack instead, but NAY! This > script: > > on openStack > put the defaultStack && the short name of the topStack & cr into msg > open stack "untitled 2" > put the defaultStack && the short name of the topStack & cr after msg > go me > put the defaultStack && the short name of the topStack & cr after msg > end openStack > > produces: > stack "Untitled 1" Untitled 1 > stack "Untitled 2" Untitled 2 > stack "Untitled 2" Untitled 2 > > After I go me, neither the defaultStack nor the topStack changes! What is > more, the untitled 2 stack still has focus!! > > Just to be certain I disabled all my plugins and relaunched, same thing. > > This CANNOT BE RIGHT! And if it is the expected behavior, it ought not be. > > Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
Okay I created a simple stack with one sub stack. In the card script of stack 1 I put the handler: on openStack put the defaultStack & cr into msg open stack "untitled 2" put the defaultStack & cr after msg open me put the defaultStack & cr after msg end openStack I get: stack "Untitled 1" stack "Untitled 2" stack "Untitled 2” It seems going,opening a stack sets the opened stack to the default… IF IT’s NOT ALREADY OPENED! If it IS, well then you are on your own. The defaultStack is the last stack opened. (I’m assuming it’s a normal stack and not a pallet or something else). Now you would think at this point you can use topStack instead, but NAY! This script: on openStack put the defaultStack && the short name of the topStack & cr into msg open stack "untitled 2" put the defaultStack && the short name of the topStack & cr after msg go me put the defaultStack && the short name of the topStack & cr after msg end openStack produces: stack "Untitled 1" Untitled 1 stack "Untitled 2" Untitled 2 stack "Untitled 2" Untitled 2 After I go me, neither the defaultStack nor the topStack changes! What is more, the untitled 2 stack still has focus!! Just to be certain I disabled all my plugins and relaunched, same thing. This CANNOT BE RIGHT! And if it is the expected behavior, it ought not be. Bob S > On Apr 18, 2020, at 12:56 PM, Mark Wieder via use-livecode > wrote: > > On 4/18/20 11:33 AM, Bob Sneidar via use-livecode wrote: > >> Until I can figure out what is causing it, I cannot trust the defaultStack. > > I think the basic lesson here is "if you're going to rely on the defaultstack > you should set the defaultstack". > > -- > Mark Wieder > ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
Hi. I know that doing the simplest things, breathing, going down to the message box, can upset the defaultStack. I see this often when trying to change properties in open inspector(s). My example may have been unfair to your issue, because I wound it so tightly within a single short handler. There was no room for fiddling around, by you or LC. When one is roaming around the IDE, I think I have seen the same things you have. Craig -Original Message- From: Bob Sneidar via use-livecode To: How to use LiveCode Cc: Bob Sneidar Sent: Sat, Apr 18, 2020 2:35 pm Subject: Re: Long Standing Issue with the defaultStack Not sure at this point. When I open a sub stack called “Devices” (or any sub stack) of my main stack “Forms Generator” and I enter “put the defaultStack” in the message box, I get “Forms Generator”. If I put the command “put the defaultStack” in the last line of the openStack handler of stack devices, I get “Devices”. Right afterwards, if I enter “put the defaultStack” in the message box, I get “Forms Generator” again! Not entirely sure what is doing it. Had the same issue with another much simpler stack. If I went invisible to a database setup stack, then went back to the stack that called it, the defaultStack remained the database setup stack, and THAT wasn’t even a sub stack! Until I can figure out what is causing it, I cannot trust the defaultStack. Bob S > On Apr 18, 2020, at 9:53 AM, dunbarx--- via use-livecode > wrote: > > Bob. > I make a new stack "XXX", and a substack "YYY", and save the lot. To be sure, > I quit LC and open "XXX" from the desktop. > There is a single button on "XXX" that:on mouseUp go stack"yyy"answer the > defaultStackend mouseUp > I get "YYY" > What are you seeing? > Craig ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
On 4/18/20 11:33 AM, Bob Sneidar via use-livecode wrote: Until I can figure out what is causing it, I cannot trust the defaultStack. I think the basic lesson here is "if you're going to rely on the defaultstack you should set the defaultstack". -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
Not sure at this point. When I open a sub stack called “Devices” (or any sub stack) of my main stack “Forms Generator” and I enter “put the defaultStack” in the message box, I get “Forms Generator”. If I put the command “put the defaultStack” in the last line of the openStack handler of stack devices, I get “Devices”. Right afterwards, if I enter “put the defaultStack” in the message box, I get “Forms Generator” again! Not entirely sure what is doing it. Had the same issue with another much simpler stack. If I went invisible to a database setup stack, then went back to the stack that called it, the defaultStack remained the database setup stack, and THAT wasn’t even a sub stack! Until I can figure out what is causing it, I cannot trust the defaultStack. Bob S > On Apr 18, 2020, at 9:53 AM, dunbarx--- via use-livecode > wrote: > > Bob. > I make a new stack "XXX", and a substack "YYY", and save the lot. To be sure, > I quit LC and open "XXX" from the desktop. > There is a single button on "XXX" that:on mouseUp go stack"yyy"answer the > defaultStackend mouseUp > I get "YYY" > What are you seeing? > Craig ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
Bob. I make a new stack "XXX", and a substack "YYY", and save the lot. To be sure, I quit LC and open "XXX" from the desktop. There is a single button on "XXX" that:on mouseUp go stack"yyy"answer the defaultStackend mouseUp I get "YYY" What are you seeing? Craig -Original Message- From: Bob Sneidar via use-livecode To: How to use LiveCode Cc: Bob Sneidar Sent: Fri, Apr 17, 2020 7:19 pm Subject: Long Standing Issue with the defaultStack Hi all. I think I have stumbled across what appears to be a bug. When I open a sub stack from a main stack script, the main stack remains the defaultStack. This is causing any number of issues with me. I have a closeStackRequest handler for instance that auto saves the stack. It never gets triggered because the closeStack message never gets sent to it! If I open a stack, shouldn’t THAT STACK become the default, barring modal or system stacks? MacOS Community 9.5.1 Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Long Standing Issue with the defaultStack
Okay wrong again. The message gets sent first to the card, then the stack, then the stack behavior, then the main stack. But before any of that, I get a dialog asking if I want to save the stack! That is what I am trying to avoid! This was discussed before, and I thought closeStackRequest was the solution, but apparently not. I may need to do this in a front script. The defaultStack thing still stands though. Bob S > On Apr 17, 2020, at 4:17 PM, Bob Sneidar via use-livecode > wrote: > > Hi all. > > I think I have stumbled across what appears to be a bug. When I open a sub > stack from a main stack script, the main stack remains the defaultStack. This > is causing any number of issues with me. I have a closeStackRequest handler > for instance that auto saves the stack. It never gets triggered because the > closeStack message never gets sent to it! > > If I open a stack, shouldn’t THAT STACK become the default, barring modal or > system stacks? > > MacOS Community 9.5.1 > > Bob S ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
