Geoff,
Thanks for the reply (and good to hear from you!) I put this in:
repeat until the effective working screenRect tRect
wait 1 tick
end repeat
If just stuck in the loop forever.
-Dan
This is just a guess, but the keyboard takes time to pop out. If you check
without waiting, the
Dan-
Saturday, August 10, 2013, 7:47:17 AM, you wrote:
If just stuck in the loop forever.
Doctor says don't do that.
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to
That seems weird. You're saying this works:
get the effective working screeRect -- keyboard is not open
-- do something that will open the keyboard
wait 20 ticks
get the effective working screeRect -- different rect because keyboard is open
But this never exits:
put the effective working
Geoff-
Saturday, August 10, 2013, 9:46:15 AM, you wrote:
If that's the case, I can only assume that there is some
threshold for waiting that allows other things to happen and one
tick isn't long enough. Still, that's odd.
Not that odd. One tick is a pretty small time slice. Maybe
wait 1 tick
On Sat, Aug 10, 2013 at 12:04 PM, Mark Wieder mwie...@ahsoftware.netwrote:
Geoff-
Saturday, August 10, 2013, 9:46:15 AM, you wrote:
If that's the case, I can only assume that there is some
threshold for waiting that allows other things to happen and one
tick isn't long enough. Still,
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
Okay, this is really weird. This barely moves the CPU needle -- 3% CPU
usage for me:
repeat 50
wait 10 ticks
end repeat
This punches the CPU pretty hard -- 20% CPU usage for me, 6x, despite it
only cycling twice as often:
repeat 100
wait 5 ticks
end repeat
Then this
This is just a guess, but the keyboard takes time to pop out. If you check
without waiting, the keyboard might not have deployed yet. I'm curious what
would happen if you did a repeat with a 1 tick delay and grabbed the text into
an array. Would it be same, same, same, same, changed all the
