Bob, Sorry I can't double check at the moment, but I was reading the release notes for 10 dp7 and there was some stuff about that in there (Its possible I am ..... mis-remembering.) Is that the version you are using?
On Wed, Mar 27, 2024 at 7:02 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Oh, but it gets better. I put at the entry point of the script: > > lock screen > put the lockscreen into tScreenIsLocked — I checked and this is true > > Then at the exit point: > > put the lockscreen > > STILL TRUE in spite of the fact that I see everything that the app is > doing to the screen the entire time. > > Also curious is that I get the same result whether or not I am in script > debug mode or no!!!!! > > Bob S > > > > On Mar 27, 2024, at 3:55 PM, Bob Sneidar <bobsnei...@iotecdigital.com> > wrote: > > > > Hi all. > > > > I read in the dictionary that Lock Screen does not work in Script Debug > mode. Okay so I turn it off, put the command “Lock Screen” at the entry > point to a selectionChanged handler which goes on to do a number of things > that change the appearance of the screen. The screen is decidedly NOT > LOCKED! The things I go on to do are things like changing the hilitedItems > of a tab widget which in turn shows and hides a number of objects, and also > changes the selection in a number of datagrids. Every action that alters > the screen is visible after I issue the Lock Screen command. > > > > Is Lock Screen completely hosed? Am I missing something?? > > > > 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
