effective working screenRect

[Mark Wieder]

Geoff-

Saturday, August 10, 2013, 1:28:11 PM, you wrote:

> I suppose, but still I would expect that a loop like that would leave
> 99.99% of whatever device it's running on free to do whatever, since that
> code is executing a max of 60 times per second, and should take the
> smallest fraction of a second to run each time.

But wait without messages is blocking, so the tight loop is using up
all of the available cpu time. Even though the wait is sitting there
for 1/60 of a second, nothing else is getting done.

-- 
-Mark Wieder
 mwieder at ahsoftware.net