ontext:
http://runtime-revolution.278305.n4.nabble.com/working-screenrect-tp4685539p4685569.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url
> John you're doing better than me - for iPhone I can't get the simulator to
> display anything except 4s (Yosemite using LC 6.5, 6.7 and 7.0) - and the
> simulator keyboard never fires either - but on a device things (so far)
> appear as they are supposed to...
>
> Dave
Well, it is a show stopp
xt:
http://runtime-revolution.278305.n4.nabble.com/working-screenrect-tp4685539p4685559.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe,
I asked this a few weeks ago. No answer.
Gerry
On Sat, 8 Nov 2014 at 5:17 am, John Dixon wrote:
> If I make a stack at 320 x 480
> Choose 'Device > iPhone 4s' from the 'Hardware' menu then :-
>
> put the item 3 to 4 of the effective working screenRect
If I make a stack at 320 x 480
Choose 'Device > iPhone 4s' from the 'Hardware' menu then :-
put the item 3 to 4 of the effective working screenRect into fld 1
returns 0,0,320,480... this is expected. I change the Device to 'iPhone 5s'
from the 'Hard
quot; & cr & the effective working screenRect
end keyboardActivated
on keyboardDeactivated
answer "keyboard deactivated" & cr & the effective working screenRect
end keyboardDeactivated
___
use-livecode mailing list
use-livecod
Greetings!
On my iPhone 4 (iOS 5.1.1), with the keyboard activated, the effective working
screenRect returns 0,0,640,744. This is obviously wrong -- 744 is not the top
of the keyboard, 528 is correct. In the simulator with iOS 7, it seems
correct. Anyone have any knowledge about this
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 sc
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
On Sat, Aug 10, 2013 at 12:04 PM, Mark Wieder wrote:
> 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.
>
>
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 ti
rking screeRect into tRect -- keyboard is not open
-- do something that will open the keyboard
repeat until the effective working screenRect <> tRect
wait 1 tick
end repeat
If that's the case, I can only assume that there is some threshold for waiting
that allows other things to happen an
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 subs
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
> wit
e know what am I doing wrong? Here's the script I am running on a
> iPhone 4 (works fine in the Simulator):
>
> put the effective working screenRect into tRect
> mobileControlCreate "multiline","myTextField"
> mobileControlSet "myTextField",
Greetings!
Anyone know what am I doing wrong? Here's the script I am running on a iPhone
4 (works fine in the Simulator):
put the effective working screenRect into tRect
mobileControlCreate "multiline","myTextField"
mobileControlSet "myTextField", "fon
Richmond wrote:
On Linux (Ubuntu 11.04 beta with GNOME) there is no difference between
the screenRect
and the working screenRect
Livecode FAILS to pick up GNOME panels, Avant Window Navigator and Docky.
I am not entirely surpised by AWN and Docky as they are add-ons; but the
failure to pick
On Wed, Feb 9, 2011 at 1:56 PM, Richmond wrote:
> Aaagh!
>
> On Linux (Ubuntu 11.04 beta with GNOME) there is no difference between the
> screenRect
> and the working screenRect
>
> Livecode FAILS to pick up GNOME panels, Avant Window Navigator and Docky.
>
> I am not e
Aaagh!
On Linux (Ubuntu 11.04 beta with GNOME) there is no difference between
the screenRect
and the working screenRect
Livecode FAILS to pick up GNOME panels, Avant Window Navigator and Docky.
I am not entirely surpised by AWN and Docky as they are add-ons; but the
failure to pick
up my
On 02/08/2011 06:29 PM, David C. wrote:
Aaar! And in Linux-land things get really wild with "desktop furniture" all
over the place.
Well, although I wouldn't recommend it (nor would I appreciate it as a
user) you could always start up using the entire screen without a
title bar, similar to the b
> Aaar! And in Linux-land things get really wild with "desktop furniture" all
> over the place.
Well, although I wouldn't recommend it (nor would I appreciate it as a
user) you could always start up using the entire screen without a
title bar, similar to the backdrop in LiveCode. Better of course,
On 02/08/2011 05:26 PM, David C. wrote:
I don't have access to Windows Vista or 7: would be most grateful if someone
could
let me know the fatness of their respective taskbars.
Hello Richmond,
I think that is a relative measurement that may not be the same on all
machines... depending on the cho
On 02/08/2011 05:23 PM, Klaus on-rev wrote:
Hi Richmond,
The working screenRect for Windows XP tells me that the XP taskBar is 30 pixels
fat:
put ((item 4 of the working screenRect) - (item 4 of the screenRect)) into
fatness
and that for Windows ME, 98 and 95 it is 28 pixels.
I don't
> I don't have access to Windows Vista or 7: would be most grateful if someone
> could
> let me know the fatness of their respective taskbars.
Hello Richmond,
I think that is a relative measurement that may not be the same on all
machines... depending on the choice of icon sizes and how the taskba
Hi Richmond,
> The working screenRect for Windows XP tells me that the XP taskBar is 30
> pixels fat:
>
> put ((item 4 of the working screenRect) - (item 4 of the screenRect)) into
> fatness
>
> and that for Windows ME, 98 and 95 it is 28 pixels.
>
> I don't h
The working screenRect for Windows XP tells me that the XP taskBar is 30
pixels fat:
put ((item 4 of the working screenRect) - (item 4 of the screenRect))
into fatness
and that for Windows ME, 98 and 95 it is 28 pixels.
I don't have access to Windows Vista or 7: would be most gratef
26 matches
Mail list logo
