Even when you lock the screen and go back to the first stack, the focus remains on the stack underneath.
Apparently LC won’t do any visual changes to a stack which is not the topStack. Possibly there are human interface guidelines in play here. Peter On Apr 24, 2016, at 4:03 PM, Mike Kerner <mikeker...@roadrunner.com> wrote: > as a workaround, can you lock the screen, do the move, and then send it > back? > > On Sun, Apr 24, 2016 at 6:58 PM, Sannyasin Brahmanathaswami < > bra...@hindu.org> wrote: > >> If you dispatch a “go next card” to a stack that is not the top stack.. >> .it immediately comes to the foreground if the calling stack is not a >> palette. >> >> Is there a way to prevent this? >> >> BR >> _______________________________________________ >> 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 > > > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > _______________________________________________ > 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
