@jbv - yes, the way you structured this is more foolproof. this is the way we set up our kiosks, because they are running in single-app mode, so if the timers stop, it will break the app. a couple of other things you can do, that might help you figure out what's going on: * put the rest of handler1 in a try/catch * check the waitDepth before proceeding.
On Mon, Mar 17, 2025 at 10:13 AM jbv via use-livecode < use-livecode@lists.runrev.com> wrote: > Le 2025-03-17 10:01, Alex Tweedly via use-livecode a écrit : > > That sounds quite likely. If handler1 is running continuously, then > > other messages will not happen. > > > > I'd suggest putting various > > > > wait for 0 seconds with messages > > > > inside the running loops of handler1, in order that pending messages > > can be dealt with. > > > > Alex. > > > > Yes, I thought of that, I even inserted numerous "handler2" commands > in handler1, but the idea was to have messages to "handler2" sent in > a very regular way, no matter what happens in handler1. > And inserting commands in handler1 will break that regularity, for > they will be scattered among the script... > > _______________________________________________ > 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
