Don't sweat the beachBall

Anything beyond the basics in using the LiveCode language. Share your handlers, functions and magic here.

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller

Post Reply
dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 9580
Joined: Wed May 06, 2009 2:28 pm
Location: New York, NY

Don't sweat the beachBall

Post by dunbarx » Wed Feb 02, 2022 9:56 pm

You have to read the last few posts (on Feb 2) in:
viewtopic.php?f=8&t=36710
If there is a lesson here, know that the beachBall of death may not mean that at all. It just means that my machine notices that a process seems, seems to be stuck, and it very well may not be.
My machine reported that LC was not responding. But that was not quite true.

Could be very useful to know...

Craig

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7215
Joined: Sat Apr 08, 2006 8:31 pm
Location: Minneapolis MN
Contact:

Re: Don't sweat the beachBall

Post by jacque » Thu Feb 03, 2022 7:07 pm

Actually it is true. When any app is in a tight loop there are no interactions with the OS. After a few seconds the OS notices and warns you. Scrolling, and other operations, apply. However when the loop finishes, communication resumes and the OS is happy again.

If you're writing your own loop, adding a "wait 0" avoids that since it gives LC a chance to do some housekeeping. But we don't have any control over the engine processes. So basically the app is "not responding".
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

Post Reply

Return to “Talking LiveCode”