On 8/14/2018 2:09 PM, Ralph DiMola via use-livecode wrote: > I just got "application is not responding" from the Win 10 Task Manager for > about 10 seconds before it came back. I don't say that LC could not improve > on this but if one of Windows core utilities can't avoid it, then in my > humble opinion LC can only mitigate it but never solve it. > Undoubtedly true, but it is still darned annoying. I was just working with an App processing 7334 records. It has a counter in a window, doing the "Preparing <count> of <total>" so I can see its progress as each record takes many seconds. At "Preparing 3541 of 7334" Windows 8.1 declared that the window was "not responding" and stopped updating the counter windows. I could tell it was still running because it also does a "set cursor to busy" after each record and while Windows switched the LiveCode beachball spinning busy cursor to its blue ring of death, if I move the cursor over a different window of the app it changed back to the spinning busy cursor and kept on spinning at the expected rate.
I think this Windows issue in 8.x and 10 impacts people doing various intensive data processing tasks the most by preventing updates to status windows while the script executes. Now trying inserting various "wait ... with messages" to see if I can get it to display the counter all the way to the end (about 1.5 hours each test!) 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
