I put the suspendStack handler in the card instead. Same thing. Seems the suspendStack message is only getting sent once for every different stack I switch to. For instance, I can click the window of the mainstack while in a substack and I get the suspendStack message. Subsequent clicks however do NOT get sent. But if I click a DIFFERENT stack, say the script editor, I DO get the suspendStack message. Subsequent clicks to ANY of the stacks, once clicked in do NOT generate a suspendStack message.
What's even more interesting is that after clicking the script editor as the second alternate window clicked (the first being the mainstack) the titlebar of the mainstack is WHITE not the usual grey 3d look, and remains this way until it becomes the only open window. I think what is happening is that the topstack gets changed the first time I click an alternate window and does not change until I close that window the way it should. That is why suspendStack is not getting sent a second time to the stack that *appears* to be on top. Another stack is the topStack. Once *ANY* stack gets a suspendStack message the first time, it never seems to get subsequent messages. I am going to add the handler to a backscript later to see who is getting the message and where it is going. Bob S > On Sep 20, 2018, at 14:53 , Brian Milby via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I just set up a couple stacks and it worked every time. Then I switched to > another application and then the messages stopped. I will need to go back and > see if I can reduce to a recipe. > > The dictionary says the message is sent to the card, so the stack should see > it. > > Thanks, > Brian > On Sep 20, 2018, 4:35 PM -0500, dunbarxx via use-livecode > <use-livecode@lists.runrev.com>, wrote: >> Hmmm. >> >> Not sure of your setup, of course, but if I try an experiment, it always >> works. Can you check the topStack each time you return to the, er, topStack? >> You may indeed need to place that handler in a backScript or stack in use in >> order to do so. >> >> Craig >> >> >> >> -- >> Sent from: >> http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html >> >> _______________________________________________ >> 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
