> On 31 May 2017, at 10:42 am, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > I think anything that is displaying properties of any controls will cause > this. It has to intercept the engine and update the displayed settings each > time anything changes. Otherwise you would not get real time updates to these > properties in any open windows.
Something like that should be able to be worked around by sending in some unnoticeable to the user amount time (I usually use 200 milliseconds) then cancel the send if the event happens again within the time. We do that all over the place but there could be a few spots that are being missed. Like this local sMessage on somethingChaged cancel sMessage send “displayChange” to me in 200 milliseconds put the result into sMessage end somethingChanged on displayChange — actually do something end displayChange Cheers Monte _______________________________________________ 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
