Got it. Thanks, Richmond.
> On Mar 19, 2021, at 2:31 AM, Richmond via use-livecode
> wrote:
>
> put the screenrects
>
> with an 's'
>
> Best, Richmond.
>
> On 18.03.21 23:28, Roger Guay via use-livecode wrote:
>> Can someone please tell me how to ge
put the screenrects
with an 's'
Best, Richmond.
On 18.03.21 23:28, Roger Guay via use-livecode wrote:
Can someone please tell me how to get the screenRect of multiple monitor setup?
Thanks,
Roger
___
use-livecode mailing list
use-livecode
:28 PM, Roger Guay via use-livecode
> wrote:
>
> Can someone please tell me how to get the screenRect of multiple monitor
> setup?
>
> Thanks,
> Roger
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
>
Can someone please tell me how to get the screenRect of multiple monitor setup?
Thanks,
Roger
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http
Ya know, I remember a good while back, several years, that in the process of
debugging I would get into these unstable states. It was something in my code
that was throwing an error, but the debugger instead of catching it and
stopping at the line, basically looked like it completed. But it
I knew once but I forgot.
Bob S
> On Mar 13, 2019, at 13:59 , Mark Wieder via use-livecode
> wrote:
>
>> Had that happened initially I would not have started this thread.
>
> I think there's a valuable lesson to be learned here.
> I'm not sure what it is.
>
> --
> Mark Wieder
>
On 3/13/19 3:59 PM, Mark Wieder via use-livecode wrote:
On 3/13/19 12:10 PM, Richmond via use-livecode wrote:
Had that happened initially I would not have started this thread.
I think there's a valuable lesson to be learned here.
I'm not sure what it is.
It sort of fits with what I've
"Have you tried turning it off and on again?"
https://www.youtube.com/watch?v=nn2FB1P_Mn8
Lagi
On Wed, 13 Mar 2019 at 20:59, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 3/13/19 12:10 PM, Richmond via use-livecode wrote:
>
> > Had that happened initially I would
Yes, there is a valuable lesson:
reel in one's impulsive nature, and don't panic.
Richmond.
On 13.03.19 22:59, Mark Wieder via use-livecode wrote:
On 3/13/19 12:10 PM, Richmond via use-livecode wrote:
Had that happened initially I would not have started this thread.
I think there's a
> > Richmond M. wrote:
> > Had that happened initially I would not have started this thread.
> Mark Wieder wrote:
> I think there's a valuable lesson to be learned here. I'm not sure
> what it is.
I wrote also things to the use-list (mostly silly typos) I wished a
few seconds later I could
On 3/13/19 12:10 PM, Richmond via use-livecode wrote:
Had that happened initially I would not have started this thread.
I think there's a valuable lesson to be learned here.
I'm not sure what it is.
--
Mark Wieder
ahsoftw...@gmail.com
___
e-livecode wrote:
What is reported with just screenRect?
Thanks,
Brian
On Mar 13, 2019, 3:05 PM -0400, Richmond via use-livecode
, wrote:
What is not working is that 1034 is the number given regardless of
whether the
words *effective* and *working* are used or not.
Richmond.
On 13.03.19 21:02, Rich
0,23,1920,1034
On 13.03.19 21:06, Brian Milby via use-livecode wrote:
What is reported with just screenRect?
Thanks,
Brian
On Mar 13, 2019, 3:05 PM -0400, Richmond via use-livecode
, wrote:
What is not working is that 1034 is the number given regardless of
whether the
words *effective
What is reported with just screenRect?
Thanks,
Brian
On Mar 13, 2019, 3:05 PM -0400, Richmond via use-livecode
, wrote:
> What is not working is that 1034 is the number given regardless of
> whether the
> words *effective* and *working* are used or not.
>
> Richmond.
>
&
What is not working is that 1034 is the number given regardless of
whether the
words *effective* and *working* are used or not.
Richmond.
On 13.03.19 21:02, Richard Gaskin via use-livecode wrote:
Richmond wrote:
> when I put
>
> *put the working screenRect *
>
> into t
Richmond wrote:
> when I put
>
> *put the working screenRect *
>
> into the msgBox I get *0,23,1920,1034*
>
> that includes the macOS Dock and the menuBar!
Menubar at the top with Dock at the bottom - that seems correct.
What is not working?
--
Richard Gaskin
Fourth Wo
So, "here" on macOS 10.14.4 beta 5 with LC 9.0.3 rc-1 [ "Edge City" as
they used to say when I wore flared jeans ],
when I put
*put the working screenRect *
into the msgBox I get *0,23,1920,1034*
that includes the macOS Dock and the menuBar!
*put the effective scre
Hi Monte,
This happens for me in a fresh instance in the IDE (LC 9.0.2 on Mac). Again, I
have a 2nd larger monitor with the bottoms aligned, placing the top of the 2nd
monitor higher than the main monitor. Then just type into the message box
"Answer hello" and the dialog positions itself almost
On 1/14/2019 7:58 PM, Knapp Martin via use-livecode wrote:
set the loc of stack "Ask Dialog" to screenLoc()
ask "What color is you favorite?”
Does that work for you Paul - it doesn’t for me. I’m having to do this:
send CenterAnswerOnScreen to me in 1 tick
answer “Blah blah blah”
on
Hi Marty
I’m just wondering if you are using the standard IDE ask and answer dialog or a
custom one? If you are working on a very old stack then MetaCard used to copy
the ask and answer dialog into the stackFile as a substack. You should be able
to see them in the project browser under your
> set the loc of stack "Ask Dialog" to screenLoc()
> ask "What color is you favorite?”
Does that work for you Paul - it doesn’t for me. I’m having to do this:
send CenterAnswerOnScreen to me in 1 tick
answer “Blah blah blah”
on CenterAnswerOnScreen
set the loc of stack "answer dialog" to the
On 1/10/2019 11:02 PM, Knapp Martin via use-livecode wrote:
OK, I’m making progress here. But I’m finding that ask and answer dialogs are
opening off-screen. How are their positions determined?
Marty
See https://quality.livecode.com/show_bug.cgi?id=4309
A very old enhancement request that
Aha! Thanks Paul, that's just what I needed. I looked through all the
'changed' messages in the dictionary but didn't spot that one.
Ben
On 14/01/2019 13:38, Paul Dupuis via use-livecode wrote:
This is the 'desktopChanged' message -- see Dictionary
On 1/14/2019 8:22 AM, Ben Rubinstein via
This is the 'desktopChanged' message -- see Dictionary
On 1/14/2019 8:22 AM, Ben Rubinstein via use-livecode wrote:
Related to this: is there any possibility of getting a
"screensChanged" message? I work on multi-monitor setups all the time,
and have not been bothered by the issue with
Related to this: is there any possibility of getting a "screensChanged"
message? I work on multi-monitor setups all the time, and have not been
bothered by the issue with screenRects because they've always told the truth
relative to each other.
However, the problem is that my set-up changes
ine (the screen of stack
> “Foo”) of the effective working screenRects
>
> — set the topLeft of a stack to the topLeft of the main screen below the
> menubar
> set the topLeft of stack “Foo” to item 1 to 2 of the effective working
> screenRect
>
> — set the loc of a st
I was probably the first person to mention it. I get around it by setting the
position of my stacks when opened or resumed to be within the bounds of the
monitor. Actually, this will happen when switching from the single built-in
display of a laptop to a dual display with the laptop closed
OK, I’m making progress here. But I’m finding that ask and answer dialogs are
opening off-screen. How are their positions determined?
Marty
> On Jan 10, 2019, at 6:44 PM, Brian Milby via use-livecode
> wrote:
>
> I do see one issue with the “effective” dictionary entry though. Normally
>
I do see one issue with the “effective” dictionary entry though. Normally you
are not able to set effective properties, but for stack rect properties it is
permitted.
topLeft and topRight also need a clarifying statement to indicate that multiple
monitors could cause the main screen topLeft
It is part of the “rectangle” property. The individual pieces are not
enumerated.
Thanks,
Brian
On Jan 10, 2019, 8:08 PM -0600, Paul Hibbert via use-livecode
, wrote:
> Interesting! - it does appear to work, but that combination is not in the
> dictionary under “topLeft” as far as I can see,
Interesting! - it does appear to work, but that combination is not in the
dictionary under “topLeft” as far as I can see, and “topLeft” is missing from
the list of properties shown under the “effective” description.
Paul
> On Jan 10, 2019, at 17:03, Brian Milby via use-livecode
> wrote:
>
>
Good catch Brian!
> On 11 Jan 2019, at 12:03 pm, Brian Milby via use-livecode
> wrote:
>
> You may want to use the “effective topLeft” though. Otherwise the title bar
> of the window could be off screen.
___
use-livecode mailing list
fective working screenRects
> >
> > — set the topLeft of a stack to the topLeft of the main screen below the
> > menubar
> > set the topLeft of stack “Foo” to item 1 to 2 of the effective working
> > screenRect
> >
> > — set the loc of a stack to the center of
put item 1 of the working screenrect into tLeft
put item 2 of the working screenrect into tTop
set the top of stack “x” to tTop
set the left of stack “x” to tLeft
I’m sure there are more efficient ways, but that is the idea. You just need to
calculate the offset from the origin manually
ects
>
> — set the topLeft of a stack to the topLeft of the main screen below the
> menubar
> set the topLeft of stack “Foo” to item 1 to 2 of the effective working
> screenRect
>
> — set the loc of a stack to the center of its screen
> local tLoc, tRect
> put li
” to item 1 to 2 of line (the screen of stack
“Foo”) of the effective working screenRects
— set the topLeft of a stack to the topLeft of the main screen below the menubar
set the topLeft of stack “Foo” to item 1 to 2 of the effective working
screenRect
— set the loc of a stack to the center of i
I was merely using that as an example. In my app I too place a toolbar in the
topLeft corner of the screen by setting the topLeft of the stack to 0,0. On a
single screen setup it works fine. But I've just discovered that on a
multi-monitor setup as I've described, the toolbar isn’t even visible
> On 11 Jan 2019, at 10:41 am, Knapp Martin via use-livecode
> wrote:
>
> When I open Livecode on my dual monitor setup where the top of the 2nd
> monitor is higher than my main monitor, both the Livecode toolbar and the
> script editor open partially off screen with their title bars
and discover some weirdness. I started
>>> with
>>>>> my displays aligned to the top and then got the screenRects and the
>>>>> screenLoc:
>>>>>
>>>>> Main screen rect: 0,0,1280,800
>>>>> 2nd screen rect: 1280,0,3200
On 1/10/2019 5:40 PM, Monte Goulding via use-livecode wrote:
I think it would be convenient to have a screenLocs variant of screenLoc so you
can:
Monte,
Funny you should say that. See hibernated enhancement request
https://quality.livecode.com/show_bug.cgi?id=21337
Paul Dupuis
e top and then got the screenRects and the
>>>> screenLoc:
>>>>
>>>> Main screen rect: 0,0,1280,800
>>>> 2nd screen rect: 1280,0,3200,1080
>>>> screenLoc: 640,400
>>>> (all as expected)
>>>>
>>>> Then I reali
gt;> (all as expected)
> >>
> >> Then I realigned the screens so that the bottoms were aligned:
> >>
> >> Main screen rect: 0,280,1280,1080
> >> 2nd screen rect: 1280,0,3200,1080
> >> screenLoc: 640,680
> >>
> >> Why would the ar
een rect: 1280,0,3200,1080
>> screenLoc: 640,400
>> (all as expected)
>>
>> Then I realigned the screens so that the bottoms were aligned:
>>
>> Main screen rect: 0,280,1280,1080
>> 2nd screen rect: 1280,0,3200,
>
> Main screen rect: 0,280,1280,1080
> 2nd screen rect: 1280,0,3200,1080
> screenLoc: 640,680
>
> Why would the arrangement of the screens effect the screenRect and
> screenLoc of the main monitor?
>
> Marty
> ___
&g
rect: 0,280,1280,1080
2nd screen rect: 1280,0,3200,1080
screenLoc: 640,680
Why would the arrangement of the screens effect the screenRect and screenLoc of
the main monitor?
Marty
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit
...@mindcrea.com*because the address
couldn't be found, or is unable to receive mail.
Thanks,
Tom
On Mon, Jul 9, 2018 at 7:04 AM, Pyyhtiä Christer via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Using LiveCode 9.0GM on Android 8.0.0, the screenRect gives 1080 x 2031,
> but the phone (Sa
Using LiveCode 9.0GM on Android 8.0.0, the screenRect gives 1080 x 2031, but
the phone (Samsung Galaxy Note 8) has 1440 x 2960. What do I do wrong?
Using LC command
set the pixelScale to the systemPixelscale
kills the app in the Android device. Removing this command makes it run
Thanks,
I added a comment to the request. Hopefully we will see this soon.
Henry
--
Sent from:
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit
prior respondent) that, in the absence of an iPhone X sized splash image,
iOS default to a compatibility mode to accommodate older apps. One
consequence of this is that iOS returns the 'older' screen size to
screenRect().
There are a number of helpful sources explaining how to approach developing
for the iPhone
I have been researching this issue and it does appear (as suggested by the
prior respondent) that, in the absence of an iPhone X sized splash image,
iOS default to a compatibility mode to accommodate older apps. One
consequence of this is that iOS returns the 'older' screen size to
screenRect
ode@lists.runrev.com> wrote:
The iPhone X screen dimensions are 375pt × 812pt. However, the LC screenRect
function returns 375 x 667 in the iPhone X simulator (LC 8.1.8, iOS 11.1,
Xcode 9.1). The difference between 812 and 667 is 145, which is the
additional height of the iPhone X screen over iPhone
, 2017 at 4:50 PM hlowe via use-livecode <
use-livecode@lists.runrev.com> wrote:
> The iPhone X screen dimensions are 375pt × 812pt. However, the LC
> screenRect
> function returns 375 x 667 in the iPhone X simulator (LC 8.1.8, iOS 11.1,
> Xcode 9.1). The difference between 812 and
The iPhone X screen dimensions are 375pt × 812pt. However, the LC screenRect
function returns 375 x 667 in the iPhone X simulator (LC 8.1.8, iOS 11.1,
Xcode 9.1). The difference between 812 and 667 is 145, which is the
additional height of the iPhone X screen over iPhone 6,7,8. The screenRect
I'm trying to figure out screen math to set the top of a helper stack to
the top of a field, and the like.
The math doesn't seem to make sense.
It would *seem* to me that
the top of this stack + the top of me
should give the top of the field in screen coordinates.
But it doesn't
So I tried
It depends if your stack has a Stack Menu or not, try…
put (the top of this stack) - (the effective top of this stack) -- With no
Stack Menu =22 with a Stack Menu = 0
Paul
On Jan 17, 2015, at 5:40 PM, Dr. Hawkins doch...@gmail.com wrote:
On Sat, Jan 17, 2015 at 4:17 PM, Scott Rossi
The difference you're seeing is likely due to the height of the stack including
its titlebar versus the height of the card region only of the stack.
You might try seeing the entries in the dictionary for localLoc and globalLoc,
used for converting global positions to local, and vice versa.
On Sat, Jan 17, 2015 at 4:17 PM, Scott Rossi sc...@tactilemedia.com wrote:
The difference you're seeing is likely due to the height of the stack
including its titlebar versus the height of the card region only of the
stack.
You might try seeing the entries in the dictionary for localLoc and
for developing an iPhone app that you would like to
run on all the iPhones from the 4s through to the 6 plus... unless of course,
pockets are deep enough to have all four of the current iPhones sitting next to
your Mac...:-(
The screenRect function is not working in the simulator...
be well
.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 to subscribe, unsubscribe and manage your subscription
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 'Hardware' menu and 0,0,320,568 is returned
I asked this a few weeks ago. No answer.
Gerry
On Sat, 8 Nov 2014 at 5:17 am, John Dixon dixo...@hotmail.co.uk 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 into fld 1
returns
.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, unsubscribe and manage your subscription
the effective working screenRect
end keyboardActivated
on keyboardDeactivated
answer keyboard deactivated cr the effective working screenRect
end keyboardDeactivated
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url
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
Richard-
Thursday, June 5, 2014, 7:19:07 AM, you wrote:
There is an IDE rewrite underway, and a very large-scope effort to
improve overall rendering.
Eh?
One of the problems with being OCD about my LiveCode consumption is that
I can no longer recall where I hear things, whether it was in
Mark Wieder wrote:
Richard-
Thursday, June 5, 2014, 7:19:07 AM, you wrote:
The IDE rewrite is AFAIK very early-stage, a logical necessity
from the Open Language initiative and the implications thereof
related to extensibility. I imagine we'll be hearing more about
it as it begins to
On 6/8/2014, 1:28 PM, Richard Gaskin wrote:
AFAIK there is no other RunRev-borne IDE in existence (the community has
several), just ideas, sketches, possibilities and imaginings which may
become fleshed out into some actual thing in the future
The idea for a new IDE was announced two RevLives
Richard-
Sunday, June 8, 2014, 11:28:28 AM, you wrote:
A secret is a willful attempt to conceal, but we have no indication that
anyone's doing that.
So before anyone runs off to the hardware store to grab pitchforks for
storming the castle over some imagined IDE conspiracy, please kindly
Mark Wieder wrote:
Richard-
Sunday, June 8, 2014, 11:28:28 AM, you wrote:
A secret is a willful attempt to conceal, but we have no indication that
anyone's doing that.
So before anyone runs off to the hardware store to grab pitchforks for
storming the castle over some imagined IDE
Mark Wieder
Richard-
Wednesday, June 4, 2014, 9:48:20 AM, you wrote:
There is an IDE rewrite underway, and a very large-scope effort to
improve overall rendering.
Eh?
One of the problems with being OCD about my LiveCode consumption is that
I can no longer recall where I hear things,
Well,
I give up.
This morning I have using LC 6.6.1 been through all my Geometry settings to
double check everything is working correctly. After a few adjustments the
Geometry settings are correct.
Set LC 6.6.1 to liveResize = false and resizable = true.
Geometry settings worked as
Terence Heaford wrote:
This morning I have using LC 6.6.1 been through all my Geometry
settings to double check everything is working correctly. After a
few adjustments the Geometry settings are correct.
Set LC 6.6.1 to liveResize = false and resizable= true.
Why set liveResizing to
Thanks for your detailed reply.
I am pretty sure Live Resizing should be the standard way of doing things but I
have to say that LC’s performance in this area is quite poor.
I have my stack at a small size to improve the scrolling speed of a table but
when I switch to another card that displays
Terence Heaford wrote:
I am pretty sure Live Resizing should be the standard way of doing
things but I have to say that LC’s performance in this area is quite
poor.
I have my stack at a small size to improve the scrolling speed of a
table but when I switch to another card that displays
Richard-
Wednesday, June 4, 2014, 9:48:20 AM, you wrote:
There is an IDE rewrite underway, and a very large-scope effort to
improve overall rendering.
Eh?
--
-Mark Wieder
ahsoftw...@gmail.com
This communication may be unlawfully collected and stored by the National
Security Agency (NSA)
Mac OS X 10.9.3 LC 6.6.1 LC 6.7 (dp4)
I have been zooming a stack to the size of the screen using the screenRect
function:
set the rect of this stack to the working screenRect
When I do this the top part of the stack window disappears beneath the OS X
menubar.
The documents suggest
In my case the working screenRect returned 0,22,1680,1046
if I add 22 to item 2 for 0,44,1680,1046 it seems to work correctly
Having measured the screen with Apples screen grab the point directly below the
OS X menubar is 22 and not 44.
Surely LC should return the correct co-ordinate for Mac
Terence Heaford wrote:
In my case the working screenRect returned 0,22,1680,1046
if I add 22 to item 2 for 0,44,1680,1046 it seems to work correctly
Having measured the screen with Apples screen grab the point directly
below the OS X menubar is 22 and not 44.
Surely LC should return
OK,
This script
put the working screenRect = the working screenRect
put return the effective working screenRect = tRect after msg
put return the screenRect = the screenRect after msg
Places the following in the msg box
the working screenRect = 0,22,1680,1046
.).
This script
put the working screenRect = the working screenRect
put return the effective working screenRect = tRect after msg
put return the screenRect = the screenRect after msg
Places the following in the msg box
the working screenRect = 0,22,1680,1046
the effective working
Sorry Richard,
set the effective rect of this stack to the working screenrect
I don’t, the traffic lights are still hidden beneath the Mac Menubar.
All the best
Terry
On 3 Jun 2014, at 19:47, Richard Gaskin ambassa...@fourthworld.com wrote:
And if you set the effective rect of the stack
Terence Heaford wrote:
Sorry Richard,
set the effective rect of this stack to the working screenrect
I don’t, the traffic lights are still hidden beneath the Mac Menubar.
All the best
Terry
On 3 Jun 2014, at 19:47, Richard Gaskin ambassador at fourthworld.com wrote:
And if you set
On 6/3/2014, 1:32 PM, Terence Heaford wrote:
the working screenRect = 0,22,1680,1046
the effective working screenRect = 0,22,1680,1046
the screenRect = 0,0,1680,1050
If I now set the rect of this stack to 0,22,1680,1046 then window
top bar that contains the traffic lights is hidden beneath
On 6/3/2014, 1:51 PM, Terence Heaford wrote:
set the effective rect of this stack to the working screenrect
I don’t, the traffic lights are still hidden beneath the Mac Menubar.
That's even better than the method I just posted. Odd it isn't working
for you, it works here. The title bar
My test agree with Richard's and confirms this as a bug in LC6.7(DP4), seems OK
in other versions so it may be something to do with the Cocoa implementation,
adding an extra line gets round the problem until it's fixed…
set the effective rect of this stack to the working screenRect
set
Greetings!
So, I have this iOS project. I run this stack in the 4-inch iPhone simulator
and the screenRect returns 0,0,320,480. How can that be? I have other
projects that report the correct value (0,0,640,960) in the same version of LC
(6.1) and Simulator (6.0).
Is there some switch I
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
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
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 and one tick isn't long
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
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, fontSize, 15
mobileControlSet myTextField, visible
!
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, fontSize, 15
mobileControlSet myTextField, visible, true
Hi all,
I made a plugin to solve this problem. You can download it from the private
section of the Economy-x-Talk homepage: http://qery.us/1fd . It is called Keep
on Screen and you can find it at the bottom of the page. A small contribution
is required to access the downloads in this section.
Anyone else who think it is annoying that windows like the message box and the
dictionary don't check whether they are inside one of the available screen
rects? Every time when I disconnects second monitor, the dictionary becomes
inaccessible!
--
Kind regards,
Mark Schonewille
Economy-x-Talk
On 12/24/2011 04:57 PM, Mark Schonewille wrote:
Anyone else who think it is annoying that windows like the message box and the
dictionary don't check whether they are inside one of the available screen
rects? Every time when I disconnects second monitor, the dictionary becomes
inaccessible!
Saw a discussion about this somewhere. Think a plugin came out of the talk,
but can't remember for sure. If I find it i'll link. (there was also a
nifty multi-montor graphic representation thingy that was really cool)
Should be pretty easy to put a plugin together to check for valid locations
Hi Mike,
I believe a desktopChanged (if that's the correct name) message is sent when a
monitor disappears or the resolution changes.
--
Kind regards,
Mark Schonewille
Economy-x-Talk
Http://economy-x-talk.com
Share the clipboard of your computer over a local network with Clipboard Link
1 - 100 of 108 matches
Mail list logo