I think they did. As I recall, the upshot was that this is a Windows thing, and Livecode is not the only victim. In fact, we use a product by Prism called DocRecord, and it will exhibit similar behavior when running on a slower PC with less than optimal resources.
I'm thinking maybe this would be a good task to hand off to some kind of agent app. It's easy to do with sockets, passing information back and forth. I wrote a Spinner app and compiled it, which would receive Applescript commands to show/hide itself, display a progress indicator, and display a status message. Since it was compiled as it's own app, it ran in it's own thread, so leaving my main app to go about it's business while it was doing it's thing. For my purposes it was only a progress dialog because an animated gif will only update while Livecode is idle, which it never is when I need a progress indicator. Bob S > On Aug 14, 2018, at 12:32 , Paul Dupuis via use-livecode > <use-livecode@lists.runrev.com> wrote: > > It would be nice if some LiveCode, Ltd expert could at least look into > this and let people know if they can do anything in their apps to avoid > this rather than leave us to try different thing hoping something we > stumble upon may work. _______________________________________________ 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
