didn't you say your code was modifying a dg? i see a couple of possible failure points: * the widget could be doing something unexpected * the dg could be unlocking the screen. you could also try two or more lock screens. i believe lock screen is additive. until idle.
On Thu, Mar 28, 2024 at 12:22 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Wow thanks for that! I think I remember now this came up before, and > datagrids were the culprit. > > But that does seem odd, doesn’t it? Why would a screen lock interfere with > the datagrid behavior? (That is rhetorical. Only the devs would know that.) > > Bob S > > > On Mar 28, 2024, at 8:48 AM, Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > there are many (many) datagrid functions and commands that unlock the > screen, > the behavior script for dg's is 11,597 lines long. > i started copying/pasting the signature of them, but finally decided there > were many too many. instead of deleting the rest of this post, i left them > in place. > i reiterate, i only went through around 2100 lines, or around 20% of the dg > behavior. i don't know how many more there are. > > _______________________________________________ > 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