Re: Multiple Displays and Screenrect

[Roger Guay via use-livecode]

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 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://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Multiple Displays and Screenrect

[Richmond via use-livecode]

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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Multiple Displays and Screenrect

[HENRY LOWE via use-livecode]

In its plural form (screenRects) this function returns a list containing

the virtual co-ordinates of all the screens currently attached to the

system. The first line is always that of the primary display, and the

order of the rest are in an OS-specific order.


Henry

> On Mar 18, 2021, at 2: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
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Multiple Displays and Screenrect

[Roger Guay via use-livecode]

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://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Bob Sneidar via use-livecode]

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 didn't. It was 
like a script was still running but I was able to interact with the UI to some 
extent. 

Bob S


> On Mar 14, 2019, at 12:31 , J. Landman Gay via use-livecode 
>  wrote:
> 
> It sort of fits with what I've seen in all versions of LC 9. Things start 
> failing inexplicably -- handlers available moments ago suddenly can't be 
> found, keyboard shortcuts stop working, the message path gets skewed or lost, 
> etc. A restart of LC fixes things until it happens again. In many cases, if I 
> don't restart, I'll eventually crash.
> 
> No recipe, no logic to it. But I think it has something to do with debugging, 
> since I most often see things go wrong after or during a debugging session.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Bob Sneidar via use-livecode]

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
> ahsoftw...@gmail.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[J. Landman Gay via use-livecode]

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 seen in all versions of LC 9. Things 
start failing inexplicably -- handlers available moments ago suddenly 
can't be found, keyboard shortcuts stop working, the message path gets 
skewed or lost, etc. A restart of LC fixes things until it happens 
again. In many cases, if I don't restart, I'll eventually crash.


No recipe, no logic to it. But I think it has something to do with 
debugging, since I most often see things go wrong after or during a 
debugging session.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Lagi Pittas via use-livecode]

"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 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
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Richmond via use-livecode]

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 valuable lesson to be learned here.
I'm not sure what it is.




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[hh via use-livecode]

> > 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 correct them.
The ability to correct things easier is one reason I like the forum
more than the use-list (relates to the environment, not the members).


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Mark Wieder via use-livecode]

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

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Richmond via use-livecode]

Having written that,and having reopened LC 9.0.3 it behaved "as it should"
and reported my screen height as 1080.

Had that happened initially I would not have started this thread.

Richmond.

On 13.03.19 21:07, Richmond wrote:

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* 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 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?


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode





___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Richmond via use-livecode]

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* 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 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?


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Brian Milby via use-livecode]

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, Richard Gaskin via use-livecode wrote:
> > 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?
> >
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Richmond via use-livecode]

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 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?



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Ineffective lazy screenRect

[Richard Gaskin via use-livecode]

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 World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Ineffective lazy screenRect

[Richmond via use-livecode]

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 screenRect*

just throws an error, and

*put the effective working screenRect*

also gives me *0,23,1920,1034*

which is not very useful at all.

Richmond.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

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 completely off screen.

I just had another customer contact me this morning complaining of the same 
issue. He's a laptop user with a 2nd large display aligned at the bottom, 
placing the top higher than the main monitor. When I had him align the tops it 
behaves fine.

Screenshots of my test:
http://martyknapp.on-rev.com/answer.html

Marty

> On Jan 14, 2019, at 7:00 PM, Monte Goulding via use-livecode 
>  wrote:
> 
> 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 mainstack. If that’s 
> the case then perhaps try deleting those.
> 
> Cheers
> 
> Monte
> 
>> On 15 Jan 2019, at 11:58 am, Knapp Martin via use-livecode 
>>  wrote:
>> 
>> 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 screenLoc
>> end CenterAnswerOnScreen
>> 
>> I have a couple of customers with small-screened laptops who use large 
>> secondary monitors aligned at the bottom. Thus the top of the secondary 
>> monitor is quite a bit above the main laptop monitor. Ask and Answer dialogs 
>> are so far off you can only see about the bottom 1/8 of an inch of the 
>> window and are thus unusable.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Paul Dupuis via use-livecode]

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 CenterAnswerOnScreen
set the loc of stack "answer dialog" to the screenLoc
end CenterAnswerOnScreen

I have a couple of customers with small-screened laptops who use large 
secondary monitors aligned at the bottom. Thus the top of the secondary monitor 
is quite a bit above the main laptop monitor. Ask and Answer dialogs are so far 
off you can only see about the bottom 1/8 of an inch of the window and are thus 
unusable.

Marty




Yes, it has been working for us. It works in LC9.0.2 with a new stack 
and a button with those 2 lines in a mouseUp handler.


I think this may only work under Desktop OSes as the Inclusions (in 
Standalone settings) show the standard Ask and Answer Dialogs available 
only for Linux, OSX, and WIndows.


Also, per prior discussion in this thread, code like:

set the loc of stack "Ask Dialog" to effectiveScreenLocOfScreen(the 
sceeen of this stack)

ask "What color?"

where

function effectiveScreenLocOfScreen pScreen
  -- pScreen is a monitor number (a line of the screenRects or the value of the 
screen of stack property
  --
  local tRect,tH,tV
  put line pScreen of the effective screenRects into tRect -- or use 'effective 
working screenRects' for accommodating pop up keyboards and such
  put ((item 3 of tRect - item 1 of tRect)/2) into tH
  put ((item 4 of tRect - item 2 of tRect)/2) into tV
  return (tH,tV)
end effectiveScreenLocOfScreen

should result in centering an Ask Dialog on the monitor that the stack that 
invokes it is on.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Monte Goulding via use-livecode]

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 mainstack. If that’s the case 
then perhaps try deleting those.

Cheers

Monte

> On 15 Jan 2019, at 11:58 am, Knapp Martin via use-livecode 
>  wrote:
> 
> 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 screenLoc
> end CenterAnswerOnScreen
> 
> I have a couple of customers with small-screened laptops who use large 
> secondary monitors aligned at the bottom. Thus the top of the secondary 
> monitor is quite a bit above the main laptop monitor. Ask and Answer dialogs 
> are so far off you can only see about the bottom 1/8 of an inch of the window 
> and are thus unusable.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

> 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 screenLoc
end CenterAnswerOnScreen

I have a couple of customers with small-screened laptops who use large 
secondary monitors aligned at the bottom. Thus the top of the secondary monitor 
is quite a bit above the main laptop monitor. Ask and Answer dialogs are so far 
off you can only see about the bottom 1/8 of an inch of the window and are thus 
unusable.

Marty

> On Jan 14, 2019, at 2:25 PM, Paul Dupuis via use-livecode 
>  wrote:
> 
> 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 would be a nice addition. SuperCard has a 
> 'at' syntax, so you could say:
> 
> Ask "What color is your favorite?" at screenLoc()
> 
> Now you have to do something like
> 
> set the loc of stack "Ask Dialog" to screenLoc()
> ask "What color is you favorite?"
> 
> The actual stack names are "Ask Dialog" and "Answer Dialog" whether invoked 
> from the IDE or a Standalone.
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Paul Dupuis via use-livecode]

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 would be a nice addition. SuperCard 
has a 'at' syntax, so you could say:


Ask "What color is your favorite?" at screenLoc()

Now you have to do something like

set the loc of stack "Ask Dialog" to screenLoc()
ask "What color is you favorite?"

The actual stack names are "Ask Dialog" and "Answer Dialog" whether 
invoked from the IDE or a Standalone.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screensChanged ? (was Re: screenRect and screenLoc weirdness)

[Ben Rubinstein via use-livecode]

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 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 screenRects because they've always told the truth 
relative to each other.


However, the problem is that my set-up changes multiple times a day. Mostly 
it's taking my laptop in and out of meetings, so switching from one 
multi-monitor set-up to single monitor; but sometimes I'm plugging it into a 
meeting room screen, and sometimes mirroring, and sometimes I end up with 
the three screens.


Many apps (including, to some extent, the LiveCode IDE) respond when this 
happens. But my own apps can't unless I specifically ask them to.


AFAICT there is no message stacks can get to tell them to get the 
screenRects again and take another look. Could there be a "screensChanged" 
or similar? (Or we could even overload "orientationChanged" for this 
purpose, although that would be probably be an error.)


Ben


On 11/01/2019 15:59, Bob Sneidar via use-livecode wrote:
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 
(built-in monitor off). If the second display is a lower resolution (as it 
likely will be with retina displays) the OS will position open windows in 
the nearest spot that can display the entire window if possible.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screensChanged ? (was Re: screenRect and screenLoc weirdness)

[Paul Dupuis via use-livecode]

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 screenRects because 
they've always told the truth relative to each other.


However, the problem is that my set-up changes multiple times a day. 
Mostly it's taking my laptop in and out of meetings, so switching from 
one multi-monitor set-up to single monitor; but sometimes I'm plugging 
it into a meeting room screen, and sometimes mirroring, and sometimes 
I end up with the three screens.


Many apps (including, to some extent, the LiveCode IDE) respond when 
this happens. But my own apps can't unless I specifically ask them to.


AFAICT there is no message stacks can get to tell them to get the 
screenRects again and take another look. Could there be a 
"screensChanged" or similar? (Or we could even overload 
"orientationChanged" for this purpose, although that would be probably 
be an error.)


Ben


On 11/01/2019 15:59, Bob Sneidar via use-livecode wrote:
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 (built-in monitor off). If the second display is a 
lower resolution (as it likely will be with retina displays) the OS 
will position open windows in the nearest spot that can display the 
entire window if possible.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

screensChanged ? (was Re: screenRect and screenLoc weirdness)

[Ben Rubinstein via use-livecode]

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 multiple times a day. Mostly 
it's taking my laptop in and out of meetings, so switching from one 
multi-monitor set-up to single monitor; but sometimes I'm plugging it into a 
meeting room screen, and sometimes mirroring, and sometimes I end up with the 
three screens.


Many apps (including, to some extent, the LiveCode IDE) respond when this 
happens. But my own apps can't unless I specifically ask them to.


AFAICT there is no message stacks can get to tell them to get the screenRects 
again and take another look. Could there be a "screensChanged" or similar? (Or 
we could even overload "orientationChanged" for this purpose, although that 
would be probably be an error.)


Ben


On 11/01/2019 15:59, Bob Sneidar via use-livecode wrote:

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 (built-in monitor 
off). If the second display is a lower resolution (as it likely will be with 
retina displays) the OS will position open windows in the nearest spot that can 
display the entire window if possible.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Bob Sneidar via use-livecode]

Thanks Monte! This will enhance the procedures I have in place! 

Bob S


> On Jan 10, 2019, at 16:39 , Monte Goulding via use-livecode 
>  wrote:
> 
> — set the topLeft of a stack to the topLeft of its screen below the menubar:
> set the topLeft of stack “Foo” 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 its screen
> local tLoc, tRect
> put line (the screen of stack “Foo”) of the screenRects into tRect
> put item 1 of tRect + (item 3 of tRect - item 1 of tRect) div 2, \
>  item 2 of tRect + (item 4 of tRect - item 2 of tRect) div 2 into tLoc
> set the loc of stack “Foo” to tLoc
> 
> — set the loc of a stack to the center of the main screen
> set the loc of stack “Foo” to the screenLoc
> 
> Hope these help! FWIW these should remain correct even if the general 
> consensus is that the desktop space should have an 0,0  origin for the main 
> screen.
> 
> Cheers
> 
> Monte

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Bob Sneidar via use-livecode]

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 (built-in monitor 
off). If the second display is a lower resolution (as it likely will be with 
retina displays) the OS will position open windows in the nearest spot that can 
display the entire window if possible. 

Bob S


> On Jan 10, 2019, at 14:29 , Tom Glod via use-livecode 
>  wrote:
> 
> i don't like how long a bug like this has been in the queue without being
> fixed. I'm surprised it hasn't affected more people but i guess maybe
> thats why its lower in the queue.
> 
> Sorry, but I don't know of any remedies for this.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

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 
> 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 to not be 0,0.
> 
> 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, 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:
>>> 
>>> “effective topLeft”
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Brian Milby via use-livecode]

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 to not be 0,0.

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, 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:
> >
> > “effective topLeft”
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Brian Milby via use-livecode]

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, 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:
> >
> > “effective topLeft”
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Paul Hibbert via use-livecode]

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:
> 
> “effective topLeft”

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Monte Goulding via use-livecode]

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
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Brian Milby via use-livecode]

You may want to use the “effective topLeft” though. Otherwise the title bar of 
the window could be off screen.

Thanks,
Brian
On Jan 10, 2019, 6:42 PM -0600, Knapp Martin via use-livecode 
, wrote:
> I will give those a spin - thanks Monte.
>
> Marty
> > On Jan 10, 2019, at 4:39 PM, Monte Goulding via use-livecode 
> >  wrote:
> >
> >
> >
> > > On 11 Jan 2019, at 11:16 am, Knapp Martin via use-livecode 
> > >  wrote:
> > >
> > > 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 it’s so far off. So in this case 0,0 is not the top left corner 
> > > of the main monitor. How so I arrive at that point? How do I determine 
> > > the actual middle of the screen? Since I don’t understand all the 
> > > dynamics of how these things are being determined I have not been able to 
> > > arrive at a work-around to place things where I’d like them on the screen.
> >
> > — set the topLeft of a stack to the topLeft of its screen below the menubar:
> > set the topLeft of stack “Foo” 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 its screen
> > local tLoc, tRect
> > put line (the screen of stack “Foo”) of the screenRects into tRect
> > put item 1 of tRect + (item 3 of tRect - item 1 of tRect) div 2, \
> > item 2 of tRect + (item 4 of tRect - item 2 of tRect) div 2 into tLoc
> > set the loc of stack “Foo” to tLoc
> >
> > — set the loc of a stack to the center of the main screen
> > set the loc of stack “Foo” to the screenLoc
> >
> > Hope these help! FWIW these should remain correct even if the general 
> > consensus is that the desktop space should have an 0,0 origin for the main 
> > screen.
> >
> > Cheers
> >
> > Monte
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Brian Milby via use-livecode]

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.  Of course you will want to wrap 
in lock screen as well.

If you want to use a different monitor, then use the screenrects and select the 
correct line.

Thanks,
Brian
On Jan 10, 2019, 6:17 PM -0600, Knapp Martin via use-livecode 
, wrote:
> 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 it’s so 
> far off. So in this case 0,0 is not the top left corner of the main monitor. 
> How so I arrive at that point? How do I determine the actual middle of the 
> screen? Since I don’t understand all the dynamics of how these things are 
> being determined I have not been able to arrive at a work-around to place 
> things where I’d like them on the screen.
>
> Marty
>
> > On Jan 10, 2019, at 3:56 PM, Monte Goulding via use-livecode 
> >  wrote:
> >
> >
> >
> > > 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 
> > > inaccessible. I understand that I can type something into the message box 
> > > to relocate them, but how is this not a bug??
> >
> > I didn’t say that wasn’t a bug. That’s an IDE script issue. Most likely a 
> > preferences issue. Have you tried resetting or trashing preferences?
> >
> > Cheers
> >
> > Monte
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

I will give those a spin - thanks Monte.

Marty
> On Jan 10, 2019, at 4:39 PM, Monte Goulding via use-livecode 
>  wrote:
> 
> 
> 
>> On 11 Jan 2019, at 11:16 am, Knapp Martin via use-livecode 
>>  wrote:
>> 
>> 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 it’s 
>> so far off. So in this case 0,0 is not the top left corner of the main 
>> monitor. How so I arrive at that point? How do I determine the actual middle 
>> of the screen? Since I don’t understand all the dynamics of how these things 
>> are being determined I have not been able to arrive at a work-around to 
>> place things where I’d like them on the screen.
> 
> — set the topLeft of a stack to the topLeft of its screen below the menubar:
> set the topLeft of stack “Foo” 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 its screen
> local tLoc, tRect
> put line (the screen of stack “Foo”) of the screenRects into tRect
> put item 1 of tRect + (item 3 of tRect - item 1 of tRect) div 2, \
>  item 2 of tRect + (item 4 of tRect - item 2 of tRect) div 2 into tLoc
> set the loc of stack “Foo” to tLoc
> 
> — set the loc of a stack to the center of the main screen
> set the loc of stack “Foo” to the screenLoc
> 
> Hope these help! FWIW these should remain correct even if the general 
> consensus is that the desktop space should have an 0,0  origin for the main 
> screen.
> 
> Cheers
> 
> Monte

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Monte Goulding via use-livecode]

> On 11 Jan 2019, at 11:16 am, Knapp Martin via use-livecode 
>  wrote:
> 
> 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 it’s so 
> far off. So in this case 0,0 is not the top left corner of the main monitor. 
> How so I arrive at that point? How do I determine the actual middle of the 
> screen? Since I don’t understand all the dynamics of how these things are 
> being determined I have not been able to arrive at a work-around to place 
> things where I’d like them on the screen.

— set the topLeft of a stack to the topLeft of its screen below the menubar:
set the topLeft of stack “Foo” 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 its screen
local tLoc, tRect
put line (the screen of stack “Foo”) of the screenRects into tRect
put item 1 of tRect + (item 3 of tRect - item 1 of tRect) div 2, \
  item 2 of tRect + (item 4 of tRect - item 2 of tRect) div 2 into tLoc
set the loc of stack “Foo” to tLoc

— set the loc of a stack to the center of the main screen
set the loc of stack “Foo” to the screenLoc

Hope these help! FWIW these should remain correct even if the general consensus 
is that the desktop space should have an 0,0  origin for the main screen.

Cheers

Monte


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

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 it’s so 
far off. So in this case 0,0 is not the top left corner of the main monitor. 
How so I arrive at that point? How do I determine the actual middle of the 
screen? Since I don’t understand all the dynamics of how these things are being 
determined I have not been able to arrive at a work-around to place things 
where I’d like them on the screen.

Marty

> On Jan 10, 2019, at 3:56 PM, Monte Goulding via use-livecode 
>  wrote:
> 
> 
> 
>> 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 inaccessible. 
>> I understand that I can type something into the message box to relocate 
>> them, but how is this not a bug??
> 
> I didn’t say that wasn’t a bug. That’s an IDE script issue. Most likely a 
> preferences issue. Have you tried resetting or trashing preferences?
> 
> Cheers
> 
> Monte

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Monte Goulding via use-livecode]

> 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 inaccessible. I 
> understand that I can type something into the message box to relocate them, 
> but how is this not a bug??

I didn’t say that wasn’t a bug. That’s an IDE script issue. Most likely a 
preferences issue. Have you tried resetting or trashing preferences?

Cheers

Monte
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

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 inaccessible. I understand that 
I can type something into the message box to relocate them, but how is this not 
a bug??

Marty

> On Jan 10, 2019, at 2:40 PM, Monte Goulding via use-livecode 
>  wrote:
> 
> Tom the issue here is that it is arguable that this is a bug. We have lots of 
> things to work on which we are sure about ;-)
> 
> To clarify what I mean. Which set of results is more correct?
> 
> Main screen rect: 0,280,1280,1080
> 2nd screen rect: 1280,0,3200,1080
> 
> Main screen rect: 0,0,1280,800
> 2nd screen rect: 1280,-280,3200,800
> 
> I think it would be convenient to have a screenLocs variant of screenLoc so 
> you can:
> 
> set the loc of this stack to line (the screen of this stack) of the screenLocs
> 
> But that’s another issue as it’s not complicated to write a function using 
> the screenRects
> 
> Cheers
> 
> Monte
> 
>> On 11 Jan 2019, at 9:29 am, Tom Glod via use-livecode 
>>  wrote:
>> 
>> i don't like how long a bug like this has been in the queue without being
>> fixed. I'm surprised it hasn't affected more people but i guess maybe
>> thats why its lower in the queue.
>> 
>> Sorry, but I don't know of any remedies for this.
>> 
>> On Thu, Jan 10, 2019 at 5:24 PM Knapp Martin via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>>> Wow, that’s been around for a while. Anybody have a work-around seeing as
>>> how this is unlikely to be fixed? Seems like setting the loc of a window to
>>> the center of the screen would be an often used feature. I never noticed it
>>> because I don’t have a multi-monitor setup.
>>> 
>>> Marty
>>> 
>>>> On Jan 10, 2019, at 1:58 PM, Tom Glod via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>>> 
>>>> Hi Marty, I saw this the other day...this is probably the bug you are
>>>> referencing.
>>>> 
>>>> https://quality.livecode.com/show_bug.cgi?id=19419
>>>> 
>>>> On Thu, Jan 10, 2019 at 3:25 PM Knapp Martin via use-livecode <
>>>> use-livecode@lists.runrev.com> wrote:
>>>> 
>>>>> So I just had a customer complain that windows were opening in odd
>>>>> locations with his multi-monitor setup: a MacBookPro with a Thunderbolt
>>>>> display. He has his displays arranged so that the bottoms were aligned
>>> with
>>>>> the 2nd display to the left of the MacBook.
>>>>> 
>>>>> So I hooked my laptop to my TV 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,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,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 this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Paul Dupuis via use-livecode]

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
Researchware

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Monte Goulding via use-livecode]

Tom the issue here is that it is arguable that this is a bug. We have lots of 
things to work on which we are sure about ;-)

To clarify what I mean. Which set of results is more correct?

Main screen rect: 0,280,1280,1080
2nd screen rect: 1280,0,3200,1080

Main screen rect: 0,0,1280,800
2nd screen rect: 1280,-280,3200,800

I think it would be convenient to have a screenLocs variant of screenLoc so you 
can:

set the loc of this stack to line (the screen of this stack) of the screenLocs

But that’s another issue as it’s not complicated to write a function using the 
screenRects

Cheers

Monte

> On 11 Jan 2019, at 9:29 am, Tom Glod via use-livecode 
>  wrote:
> 
> i don't like how long a bug like this has been in the queue without being
> fixed. I'm surprised it hasn't affected more people but i guess maybe
> thats why its lower in the queue.
> 
> Sorry, but I don't know of any remedies for this.
> 
> On Thu, Jan 10, 2019 at 5:24 PM Knapp Martin via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> Wow, that’s been around for a while. Anybody have a work-around seeing as
>> how this is unlikely to be fixed? Seems like setting the loc of a window to
>> the center of the screen would be an often used feature. I never noticed it
>> because I don’t have a multi-monitor setup.
>> 
>> Marty
>> 
>>> On Jan 10, 2019, at 1:58 PM, Tom Glod via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> Hi Marty, I saw this the other day...this is probably the bug you are
>>> referencing.
>>> 
>>> https://quality.livecode.com/show_bug.cgi?id=19419
>>> 
>>> On Thu, Jan 10, 2019 at 3:25 PM Knapp Martin via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
>>>> So I just had a customer complain that windows were opening in odd
>>>> locations with his multi-monitor setup: a MacBookPro with a Thunderbolt
>>>> display. He has his displays arranged so that the bottoms were aligned
>> with
>>>> the 2nd display to the left of the MacBook.
>>>> 
>>>> So I hooked my laptop to my TV 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,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,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 this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Tom Glod via use-livecode]

i don't like how long a bug like this has been in the queue without being
fixed. I'm surprised it hasn't affected more people but i guess maybe
thats why its lower in the queue.

Sorry, but I don't know of any remedies for this.

On Thu, Jan 10, 2019 at 5:24 PM Knapp Martin via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Wow, that’s been around for a while. Anybody have a work-around seeing as
> how this is unlikely to be fixed? Seems like setting the loc of a window to
> the center of the screen would be an often used feature. I never noticed it
> because I don’t have a multi-monitor setup.
>
> Marty
>
> > On Jan 10, 2019, at 1:58 PM, Tom Glod via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Hi Marty, I saw this the other day...this is probably the bug you are
> > referencing.
> >
> > https://quality.livecode.com/show_bug.cgi?id=19419
> >
> > On Thu, Jan 10, 2019 at 3:25 PM Knapp Martin via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >> So I just had a customer complain that windows were opening in odd
> >> locations with his multi-monitor setup: a MacBookPro with a Thunderbolt
> >> display. He has his displays arranged so that the bottoms were aligned
> with
> >> the 2nd display to the left of the MacBook.
> >>
> >> So I hooked my laptop to my TV 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,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,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 this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

Wow, that’s been around for a while. Anybody have a work-around seeing as how 
this is unlikely to be fixed? Seems like setting the loc of a window to the 
center of the screen would be an often used feature. I never noticed it because 
I don’t have a multi-monitor setup.

Marty

> On Jan 10, 2019, at 1:58 PM, Tom Glod via use-livecode 
>  wrote:
> 
> Hi Marty, I saw this the other day...this is probably the bug you are
> referencing.
> 
> https://quality.livecode.com/show_bug.cgi?id=19419
> 
> On Thu, Jan 10, 2019 at 3:25 PM Knapp Martin via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> So I just had a customer complain that windows were opening in odd
>> locations with his multi-monitor setup: a MacBookPro with a Thunderbolt
>> display. He has his displays arranged so that the bottoms were aligned with
>> the 2nd display to the left of the MacBook.
>> 
>> So I hooked my laptop to my TV 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,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,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 this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screenRect and screenLoc weirdness

[Tom Glod via use-livecode]

Hi Marty, I saw this the other day...this is probably the bug you are
referencing.

https://quality.livecode.com/show_bug.cgi?id=19419

On Thu, Jan 10, 2019 at 3:25 PM Knapp Martin via use-livecode <
use-livecode@lists.runrev.com> wrote:

> So I just had a customer complain that windows were opening in odd
> locations with his multi-monitor setup: a MacBookPro with a Thunderbolt
> display. He has his displays arranged so that the bottoms were aligned with
> the 2nd display to the left of the MacBook.
>
> So I hooked my laptop to my TV 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,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,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 this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

screenRect and screenLoc weirdness

[Knapp Martin via use-livecode]

So I just had a customer complain that windows were opening in odd locations 
with his multi-monitor setup: a MacBookPro with a Thunderbolt display. He has 
his displays arranged so that the bottoms were aligned with the 2nd display to 
the left of the MacBook.

So I hooked my laptop to my TV 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,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,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 this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect

[Tom Glod via use-livecode]

Hi, I'm sorry I cannot help you in this regard, I'm sure someone else will
be able to help with the pixel scaling issue. you have.

but FYI.I did try to send you an email in regards to your work with LC
and it bounced back.

Address not found
Your message wasn't delivered to *cris...@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 (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
> with no problem.
>
> rgds
>
> Christer Pyyhtiä
> MindCrea Ltd
> chris...@mindcrea.com
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

ScreenRect

[Pyyhtiä Christer via use-livecode]

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 with 
no problem.

rgds

Christer Pyyhtiä
MindCrea Ltd
chris...@mindcrea.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhone X Screen Dimensions and the screenRect function

[hlowe via use-livecode]

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 this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhone X Screen Dimensions and the screenRect function

[panagiotis merakos via use-livecode]

Yes, there is an enhancement request about it:

http://quality.livecode.com/show_bug.cgi?id=20641

On Nov 19, 2017 18:22, "hlowe via use-livecode" <
use-livecode@lists.runrev.com> wrote:

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().

There are a number of helpful sources explaining how to approach developing
for the iPhone X screen:

https://developer.apple.com/ios/human-interface-
guidelines/overview/iphone-x/

https://infinum.co/the-capsized-eight/how-to-prepare-mobile-app-new-iPhone-x

Adapting an app for the iPhone X using the "safe area" approach is
problematic if one cannot get the correct screenRect. I support various
screen sizes and orientations in my apps by directly redrawing the UI rather
that using the FullScreenMode property. Cannot do this without the correct
screen rect.

Is adding an iPhone X splash image in the Standalone Application Setting
dialog in the works?

Thanks,

Henry

Ascriva Health Informatics
https://www.ascriva.com





--
Sent from: http://runtime-revolution.278305.n4.nabble.com/
Revolution-User-f278306.html

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhone X Screen Dimensions and the screenRect function

[hlowe via use-livecode]

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().

There are a number of helpful sources explaining how to approach developing
for the iPhone X screen:

https://developer.apple.com/ios/human-interface-guidelines/overview/iphone-x/

https://infinum.co/the-capsized-eight/how-to-prepare-mobile-app-new-iPhone-x

Adapting an app for the iPhone X using the "safe area" approach is
problematic if one cannot get the correct screenRect. I support various
screen sizes and orientations in my apps by directly redrawing the UI rather
that using the FullScreenMode property. Cannot do this without the correct
screen rect.

Is adding an iPhone X splash image in the Standalone Application Setting
dialog in the works?

Thanks,

Henry 
 
Ascriva Health Informatics 
https://www.ascriva.com





--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhone X Screen Dimensions and the screenRect function

[J. Landman Gay via use-livecode]

Would that be the height of the notch? Apple doesn't want apps to use that 
area.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



On November 18, 2017 4:51:55 PM hlowe via use-livecode 
 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 6,7,8. The screenRect
function returns the correct screen dimensions for other iPhones in the
simulator. Is this a bug or am I missing something?

Thanks,

Henry

Ascriva Health Informatics
https://www.ascriva.com





--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iPhone X Screen Dimensions and the screenRect function

[Brian Milby via use-livecode]

My guess is that until we can provide a correctly sized Splash Screen that
the engine on the phone is going to see the iPhone 6 size.  You can see the
same thing if you do not provide any splash screens and the size will be
like the 4 inch (which is the default that is included).

On Sat, Nov 18, 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 667 is 145, which is the
> additional height of the iPhone X screen over iPhone 6,7,8. The screenRect
> function returns the correct screen dimensions for other iPhones in the
> simulator. Is this a bug or am I missing something?
>
> Thanks,
>
> Henry
>
> Ascriva Health Informatics
> https://www.ascriva.com
>
>
>
>
>
> --
> Sent from:
> http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

iPhone X Screen Dimensions and the screenRect function

[hlowe via use-livecode]

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
function returns the correct screen dimensions for other iPhones in the
simulator. Is this a bug or am I missing something?

Thanks,

Henry

Ascriva Health Informatics
https://www.ascriva.com





--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screen math, stacks, fields, and effective screenRect

[Paul Hibbert]

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  wrote:
> 
> On Sat, Jan 17, 2015 at 4:17 PM, Scott Rossi  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
>> globalLoc, used for converting global positions to local, and vice versa.
>> 
> 
> Those are definitely what I needed.
> 
> But I'm still baffled by things like the effective top being a smaller
> number (higher on the screen) than the top.
> 
> 
> 
> 
> -- 
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screen math, stacks, fields, and effective screenRect

[Dr. Hawkins]

On Sat, Jan 17, 2015 at 4:17 PM, Scott Rossi  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
> globalLoc, used for converting global positions to local, and vice versa.
>

Those are definitely what I needed.

But I'm still baffled by things like the effective top being a smaller
number (higher on the screen) than the top.




-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: screen math, stacks, fields, and effective screenRect

[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. 

Regards,

Scott Rossi 
Creative Director 
Tactile Media, UX/UI Design 

On Jan 17, 2015, at 3:58 PM, Dr. Hawkins  wrote:

> 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 effective rect and the like.
> 
> How can the effective top of a stack be *smaller* than the stack itself
> (higher on the screen).  Shouldn't it be greater due to the window
> handle/bar, whatever that is?
> 
> -- 
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

screen math, stacks, fields, and effective screenRect

[Dr. Hawkins]

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 effective rect and the like.

How can the effective top of a stack be *smaller* than the stack itself
(higher on the screen).  Shouldn't it be greater due to the window
handle/bar, whatever that is?

-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: working screenrect

[Dave Kilroy]

I'm not quite at the stage where it is essential to check on iPhone 6 etc so
am going on trust for the moment - I had been expecting another release from
LiveCode on Friday which would fix these bugs - but there must have been a
hiccup - am now hoping the release will appear Monday...

I currently have a 4s, if they don't fix it soon I'll have to get a 2nd hand
iPhone 5 (never mind a 6) for testing purposes - ho hum


John Dixon wrote
> Well, it is a show stopper 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...:-(





-
"Some are born coders, some achieve coding, and some have coding thrust upon 
them." - William Shakespeare & Hugh Senior

--
View this message in context: 
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 to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

RE: working screenrect

[John Dixon]

> 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 stopper 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
  
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: working screenrect

[Dave Kilroy]

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



John Dixon wrote
> However the same 0,0,320,568 is returned if I choose iPhone 6 or iPhone 6
> plus from the 'Hardware' menu...





-
"Some are born coders, some achieve coding, and some have coding thrust upon 
them." - William Shakespeare & Hugh Senior

--
View this message in context: 
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, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: working screenrect

[Gerry]

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 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... this too is
> expected... However the same 0,0,320,568 is returned if I choose iPhone 6
> or iPhone 6 plus from the 'Hardware' menu...
>
> Anyone else seeing this ?... Anyone got a fix so I could know which iPhone
> the stack is running on ?
>
> thanks
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

working screenrect

[John Dixon]

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... this too is expected... 
However the same 0,0,320,568 is returned if I choose iPhone 6 or iPhone 6 plus 
from the 'Hardware' menu...

Anyone else seeing this ?... Anyone got a fix so I could know which iPhone the 
stack is running on ?

thanks
  
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

iOS and effective working screenRect

[Jim sims]

When I add the following to my iOS app I get the same results (0,0,640,704)
for each.
Not helpful.

How do i get the loc or top of the keyboard (in 3.5, 4.0, and iPad sizes)
so i can properly move fields out of the way of the keyboard?


on keyboardActivated
answer "keyboard activated" & cr & 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 to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

iOS and the effective working screenRect

[Dan Friedman]

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?

Using LC version 6.1.3.

Thanks!!
-Dan
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

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 conspiracy, please kindly
take a moment to consider only what I wrote


Here is what you wrote:


There is an IDE rewrite underway, and a very large-scope effort to
improve overall rendering.


One of the problems with my admittedly-lengthy writing style is that it 
can make posts too long to read - I had also written:


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 move from sketchpad to code, but right now
it's all about supporting OL so I don't believe there's much
concrete that can be said about it until OL gets fleshed out more.

AFAIK there is no version of the engine in any usable form that supports 
Open Language (on the contrary, I would imagine there are many deep 
design decisions still being fleshed out), so it would not be possible 
for the folks at RunRev to be secretly using an IDE dependent on it.


As Jacque noted, the core dev team has been discussing plans for a new 
IDE for a long time.


Evolution of features and design are an inherent part of the process for 
all software, and a glance at the Road Map makes it clear that it will 
only become increasingly necessary for RunRev as well.


I just think it'll be more productive if we can discuss future 
development options with a presumption of good intentions.




As you know, I've been pushing for open-sourcing the IDE for over a
year now, but so far I've seen no move in that direction. If you're
privy to some information that the rest of us are not, then perhaps
you have a better word for it than "secret", because it's certainly
news to me.


If something is merely unknown, using "unknown" may be a good choice. :)

As the current acting Community Manager, the nature of the role requires 
me to help find ways to remove obstacles that may be preventing anyone 
from doing what they want to do in this open source project.


To recap where we are with the IDE in terms of open source process:


The IDE files are on GitHub, and even better are licensed under the very 
permissive MIT license:



We use LiveCode because it represents a very different way of working, 
but that same benefit for us poses unique challenges as an open source 
project.


As you know better than most, off-the-shelf versioning systems don't 
handle LiveCode's unique structure for stack files, leaving it for us to 
invent our own way to make that happen.


Good work has been done along those lines (and a lot of that by you - 
thank you for helping to bring it as far as it's come), and many options 
exist for ways to do productive work even now, before we have an even 
better system in place.


But ultimately the bigger issue here isn't a technical one of all, but 
the central challenge with all open source projects:  Finding people 
with the time and skills to contribute.


The skills required go beyond just LiveCode proficiency.  As with any 
open source project, there has to be a willingness to work within a wide 
range of divergent interests and goals, and a sometimes-dizzying variety 
of design visions.


Very few of us in the LiveCode universe have much hands-on experience 
with this sort of process.  I've made only modest contributions to the 
Ubuntu project (and thankfully none of them in C++ code ), most of 
LiveCode's user base makes and uses only proprietary software, and 
RunRev themselves have been open source just over a year.  We're all 
learning as we go.


It complicates things further that the nature of LiveCode stack files 
currently precludes us from easily using off-the-shelf systems to help 
support the process.


But I still believe we can do it.

There are some very smart, inventive people both here in the community 
and on the core dev team, and we all share the common vision of both 
sides working together productively to make the best LiveCode the world 
has seen.


To help this along, we have the good fortune of having bugs in the IDE, 
which are of course annoying but also allow us an opportunity:


If we prioritize addressing bugs in the current IDE right now, we'll not 
only have fewer bugs, but more importantly we will have found the team 
members and processes that can guide bigger objectives.


This email has already gotten too long, so let me outline some of the 
ways we can work on the IDE today in a separate post.


--
   Richard Gaskin
   LiveCode Community Manager
   richard at livecode.org

___
use-livecode mailing list
use-livecode@lists.runrev.com
P

Re: ScreenRect bug or not

[Mark Wieder]

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
> take a moment to consider only what I wrote

Here is what you wrote:

> There is an IDE rewrite underway, and a very large-scope effort to
> improve overall rendering.

As you know, I've been pushing for open-sourcing the IDE for over a
year now, but so far I've seen no move in that direction. If you're
privy to some information that the rest of us are not, then perhaps
you have a better word for it than "secret", because it's certainly
news to me.

I recall some years ago there was a decision by the team to rewrite
the datatbase library, and so all existing database bugs were "closed"
and made duplicates of a single db-rewrite bug. To date all those bug
reports remain in the limbo of duplicate entries and the database
layer has not been rewritten. I trust it will happen someday, but in
the meantime I'm not about to try fixing database layer bugs just to
have them closed as duplicates. And I don't see any difference with
the rest of the IDE if we don't know what parts are being rewritten.

...although possibly you mean something else by "IDE rewrite"...

-- 
-Mark Wieder
 ahsoftw...@gmail.com

This communication may be unlawfully collected and stored by the National 
Security Agency (NSA) in secret. The parties to this email do not 
consent to the retrieving or storing of this communication and any 
related metadata, as well as printing, copying, re-transmitting, 
disseminating, or otherwise using it. If you believe you have received 
this communication in error, please delete it immediately.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[J. Landman Gay]

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 ago (the time you 
missed Richard, but you sent a video and a random drawing prize.) I 
thought the new project browser was the first step in that direction. 
Then other things came up with more urgency and the PB is, so far, the 
only piece we have.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

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 move from sketchpad to code, but right now
>> it's all about supporting OL so I don't believe there's much
>> concrete that can be said about it until OL gets fleshed out more.
>
> If there's a secret project going on behind the scenes to produce a
> new IDE, out of sight of the github process, then it's hardly worth
> the effort to ferret out fixes to existing bugs.

Mark, you're one of the smartest people I know, so I'm having a hard 
time understanding why would you choose such an unnecessarily 
emotionally-laden word like "secret"?


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 
take a moment to consider only what I wrote, and I'll try to make it 
even clearer here:


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 once Open 
Language is far enough along to make such a necessary change in the IDE 
to support it achievable.


And as we all know, Open Language is among the least-urgent of all the 
Kickstarter goals, so don't expect it before critical fixes like 
Unicode, Cocoa, and multimedia are solidly completed.


And don't expect any IDE that depends on Open Language until Open 
Language is far enough along to be dependable.


So in the meantime, the core dev team uses the same IDE as the rest of us.

And even when a new IDE project can be started on the foundation of a 
nearly-completed Open Language-based engine, we can anticipate that 
moment will be many months from now, and will take many months more to 
complete, so any work done on the current IDE seems likely to have a 
useful shelf life.


--
  Richard Gaskin
  LiveCode Community Manager
  richard at livecode.org

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Mark Wieder]

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 a 
> newsletter article, a blog post, or the Global Jam chats Kevin and Ben
> hosted.

> 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
> move from sketchpad to code, but right now it's all about supporting OL
> so I don't believe there's much concrete that can be said about it until
> OL gets fleshed out more.

If there's a secret project going on behind the scenes to produce a
new IDE, out of sight of the github process, then it's hardly worth
the effort to ferret out fixes to existing bugs.

-- 
-Mark Wieder
 ahsoftw...@gmail.com

This communication may be unlawfully collected and stored by the National 
Security Agency (NSA) in secret. The parties to this email do not 
consent to the retrieving or storing of this communication and any 
related metadata, as well as printing, copying, re-transmitting, 
disseminating, or otherwise using it. If you believe you have received 
this communication in error, please delete it immediately.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

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, whether it was in a 
newsletter article, a blog post, or the Global Jam chats Kevin and Ben 
hosted.


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 
move from sketchpad to code, but right now it's all about supporting OL 
so I don't believe there's much concrete that can be said about it until 
OL gets fleshed out more.


The rendering optimization has been ongoing for many builds, begun with 
acceleratedRendering and tiling, and continued with the introduction of 
Skia as the 2D graphics subsystem.  Because Skia is layer-based, the 
benefits of the tiling method are somewhat limited, so the team is 
exploring a more with-the-Skia-grain approach of focusing on buffered 
layers instead.  I'm not familiar with the intricacies, but given that 
so much of LiveCode's logic is layer-based I have to imagine this will 
bode well as a more flexible approach over the long term.


Much of the initial rendering optimization was focused on the needs of 
mobile platforms, but as Kevin reminds us most of the engine stuff for 
mobile tends to benefit all platforms.  Desktop apps are increasingly 
using dynamic Metro-style layouts, and even now we can see significant 
improvement with things like moving multiple objects simultaneously 
(even on Linux, where rendering speeds used to be abysmal).


I don't know the specific status of the layer-based optimization (maybe 
it's on those Global Jam chat videos), but I'm sure we'll be hearing 
more about it as it gets further along, either in the daily blog posts 
or the newsletter.


--
 Richard Gaskin
 LiveCode Community Manager
 rich...@livecode.org

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[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?

-- 
-Mark Wieder
 ahsoftw...@gmail.com

This communication may be unlawfully collected and stored by the National 
Security Agency (NSA) in secret. The parties to this email do not 
consent to the retrieving or storing of this communication and any 
related metadata, as well as printing, copying, re-transmitting, 
disseminating, or otherwise using it. If you believe you have received 
this communication in error, please delete it immediately.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

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 charts it is
> sometimes preferable to have a larger chart which I have created in
> a group. I have to redraw the charts when the stack is resized and
> this is where LC’s performance is poor. The stack stutters slightly
> as it is resizing.

I've seen things like that now and then, rarely as bad as Apple's Garage 
Band but below what I like to give to customers.


Fortunately, in each case I found things I was doing in my scripts that 
caused redundant redraws - once I fixed those, even complex layouts with 
multiple DataGrids were pretty smooth.


DataGrids are a very challenging case, consisting as they do of so many 
controls.  Since you're only using the native field object I'll bet we 
can get your layout resizing very nicely.


Are you able to post the stack somewhere, or at least the resizeStack 
handler so we can see what it's doing?



> Now for some heresy. I also have Xojo (purchased with the last offer
> for £12) with the same programme running and this does not have the
> stutter LC does.

You won't hear cries of "heretic!" from me.  Most of us use multiple 
languages.  I've been in the biz long enough that I no longer use 
proprietary formats for anything I care about (seen too many apps come 
and go, and I need to truly own my data), but the other half of my time 
is spent in JavaScript, and lately a lot of bash.  Learning new things 
keeps us youthful. :)


Each language exists becomes it does something better than the others, 
but none of them is a magic pony, not even LiveCode, nor Objective C nor 
anything else.


In terms of performance, with Xojo's data typing requirements we'd 
expect better performance in some areas of raw computation, like image 
convolvers.  But in other areas, like text parsing, the showdown we had 
here a while back was more or less a wash, which we would also expect 
because much of what we do in LiveCode is really just triggering 
highly-optimized routines in the engine that were written in C++ and 
compiled with the super-smart Clang.


Rendering is in many respects language-independent, driven by factors 
far more complex taking place at a higher level of the implementation.



> I really prefer scripting to Objective-C and Xojo because I have
> worked with SC for so long but always seem to come up against a
> performance limitation at some point. Ah well.

In recent years Mark Lucas has done some great work on SC, and if it 
covered as many platforms as LiveCode I'd probably still be using it 
today.  But Mr. Lucas is very passionate about OS X, and his opinion 
about Windows and its API is, well, let's just say not suitable for 
posting here. :)



> I don’t know if you remember the discussions over DataGrid and the
> Basic Table Field but pending release of the update to the Basic
> Table Field to include for right alignment I have changed to this
> control because of the improved scrolling speed when compared to
> the DataGrid.
>
> Interestingly while testing the stack in LC 6.7(dp4) I have noticed
> a significant increase in scrolling speed of the Basic TableField in
> the order of a 15-25% improvement when compared to LC 6.6.1.
>
> Within this stack I have pie charts created out of LC objects and
> having just measured the milliseconds from the start of creation to
> display, there is a 12% improvement comparing LC 6.7 with LC 6.6.1.

Not surprising, given the attention the team has been putting into the 
rendering algos.


Have you benchmarked 6.6.2rc6?  While the changes aren't as deep as in 
later test versions, you may still see a boost from improvements to the 
tiling algo they use.



> I am presuming this is because of a change to Cocoa and streamlining
> the base code of LC.

Not necessarily.  In fact, I'd be surprised if Cocoa made very many 
things faster in itself, since Cocoa is only optimized for 
strictly-HIG-compliant layouts, and doesn't play nice with the sort of 
flexibility LiveCoders demand.


For example, consider the infamous pulsing default button:

Any animated effect will take more CPU load than a static one, and even 
Apple's best effort in their own apps tends to bump CPU load by about 
8-9% whenever a pulsing default button is visible on screen.


But their API for this insists on antialiasing only against a blank 
region of the window using whatever default background pattern/color 
they happen to be using in that version.


Try telling anyone using an xTalk that they can't put a default button 
on top of a graphic, or an image, or even a movie if they like.


We xTalkers are used to having this level of flexibility, but it would 
mean antialiasing artifacts if the engine used only the OS routines.


So instead the engine has to 

Re: ScreenRect bug or not

[Terence Heaford]

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 charts it is sometimes preferable 
to have a larger chart which I have created in a group. I have to redraw the 
charts when the stack is resized and this is where LC’s performance is poor. 
The stack stutters slightly as it is resizing.

Now for some heresy. I also have Xojo (purchased with the last offer for £12) 
with the same programme running and this does not have the stutter LC does.

I just mentioned this to eliminate my computer (Macbook Pro 2.4 late 2008 
unibody, hopefully due for change this summer) from the equation.

I really prefer scripting to Objective-C and Xojo because I have worked with SC 
for so long but always seem to come up against a performance limitation at some 
point. Ah well.

I don’t know if you remember the discussions over DataGrid and the Basic Table 
Field but pending release of the update to the Basic Table Field to include for 
right alignment I have changed to this control because of the improved 
scrolling speed when compared to the DataGrid.

Interestingly while testing the stack in LC 6.7(dp4) I have noticed a 
significant increase in scrolling speed of the Basic TableField in the order of 
a 15-25% improvement when compared to LC 6.6.1.

Within this stack I have pie charts created out of LC objects and having just 
measured the milliseconds from the start of creation to display, there is a 12% 
improvement comparing LC 6.7 with LC 6.6.1.

I am presuming this is because of a change to Cocoa and streamlining the base 
code of LC.

This is a significant improvement which I hope would be maintained and perhaps 
improved further as the Cocoa based LC progresses?

Do you know which version will be the first to receive the right alignment in 
the Basic Table Field?

Also while on the subject of speed (perhaps another thread) but is there an 
intention to speed up the script editor as I find the scrolling painful?

All the best

Terry


On 4 Jun 2014, at 15:57, Richard Gaskin  wrote:

> I should note that as valuable as it is for all of us to help with testing, 
> v6.7 is a VERY exotic build, the first that uses Cocoa, meaning the first to 
> attempt to merge LiveCode's object and messaging model with the limited and 
> often strictly-enforced Cocoa way of doing things.
> 
> While you're still learning the nuances of all the flexibility LiveCode 
> provides for window metrics, it may be best to stick with 6.6.2, which is 
> also a test build but without the extreme changes Cocoa requires, and also 
> very late-stage to it's quite stable and enjoyable to work with, in my 
> experience.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

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 false?  Live resizing is very much the 
convention these days.  Even Apple's Garage Band, which has the slowest 
resizing behavior I've ever seen, does live resizing.


LiveResizing doesn't affect metrics; all it does it allow your stack to 
receive resizeStack events during the resize, rather than just getting 
one message when the resizing has completed.


> Clicked on the green traffic light and the stack window zoomed to a
> very odd size with the bottom right set to the bottom right of the
> screen with a gap on the left similar to the width of the tools
> palette(which is on screen)with a similar gap between the underside
> of the menubar and the top of the stack window (icon palette not on
> screen).

This is not a bug, but a design decision.  I don't agree with it myself, 
at least not as far as the left edge goes, but it's only this way in the 
IDE and is fully settable by the scripter.


The key here is the windowBoundingRect global property - worth a visit 
to the Dictionary.  By default it should be set to give you an 
appropriate full-screen zoom without modification, but you can modify it 
to accommodate things like toolbars if you like, which is what RunRev 
has done in the IDE.


Personally I think they should have left the left edge well enough alone 
(after all, the Tool palette is movable, and really only needed for a 
relatively short time during development, in the early stages when 
you're still laying out controls).  But the top modification is 
essential, for the reasons the windowBoundingRect was added, to allow us 
to support zoomable windows that don't submarine below the toolbar.



> Gave up at that point and switched to LC 6.7 (dp 4)
>
> LC 6.7 still has liveResize = false and resizable = true.

Both of those properties are persistent so it's good to know they're 
being preserved as expected even in that deeply-modified test version.



> Dragging by the bottom right of the stack window I noticed that
> liveResize was active despite the setting being false? Is that
> another bug?

If it's a newly created stack you'll find that liveResizing is now on by 
default for the last several versions.  It really is the norm, so this 
decision just makes it one step easier for us to make modern-looking 
apps, and as I noted doesn't affect metrics in any way, only the 
frequency of resizeStack messages.


If this is a stack which had its liveResizing off in earlier builds, and 
still shows liveResizing off even though it's exhibiting this behavior, 
this may be yet another case where Cocoa's assumption that the only 
thing you'll ever want to do is complete compliance with the OS X Human 
Interface Guidelines is making it hard to do anything else, and would 
warrant a bug report if one hasn't been filed for that test build already.


I should note that as valuable as it is for all of us to help with 
testing, v6.7 is a VERY exotic build, the first that uses Cocoa, meaning 
the first to attempt to merge LiveCode's object and messaging model with 
the limited and often strictly-enforced Cocoa way of doing things.


While you're still learning the nuances of all the flexibility LiveCode 
provides for window metrics, it may be best to stick with 6.6.2, which 
is also a test build but without the extreme changes Cocoa requires, and 
also very late-stage to it's quite stable and enjoyable to work with, in 
my experience.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Terence Heaford]

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 expected when dragging the bottom right of the 
stack window.

Clicked on the green traffic light and the stack window zoomed to a very odd 
size with the bottom right set to the bottom right of the screen with a gap on 
the left similar to the width of the tools palette(which is on screen)with a 
similar gap between the underside of the menubar and the top of the stack 
window (icon palette not on screen).

Gave up at that point and switched to LC 6.7 (dp 4)

LC 6.7 still has liveResize = false and resizable = true.

Assumed Geometry settings will not have changed.

Dragging by the bottom right of the stack window I noticed that liveResize was 
active despite the setting being false? Is that another bug?

Clicked on the green traffic light and the stack window resized to what I 
expected, that is directly beneath the menubar and the size of the screen.

I cannot identify what is wrong with the resizing of stack windows as for me 
there is no discernible pattern but clearly there is something amiss.

I hope it gets cleared up in the not to distant future.


All the best

Terry



On 3 Jun 2014, at 20:51, Paul Hibbert  wrote:

> 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…

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Paul Hibbert]

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 the loc of this stack to (item 1 of the screenLoc),(item 2 of the 
screenLoc + 20) -- Temp fix for LC6.7(DP4) bug

Tested on Mac OS X 10.8.5

Paul

On 2014-06-03, at 12:11 PM, "J. Landman Gay"  wrote:

> 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 is snugged up against the bottom of the Mac 
> system menu.
> 
> -- 
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[J. Landman Gay]

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 is snugged up against the bottom 
of the Mac system menu.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[J. Landman Gay]

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 the Mac
Menubar.

If I change it to "set the rect of this stack to 0,44,1680,1046” then
the traffic lights are positioned correctly below the Mac Menubar.


I think what you want is "the effective rect of this stack". The rect of 
the stack gives you the dimensions including the title bar. The 
effective rect gives you only the content dimentions. If you subtract 
item 2 of the effective stack rect from item 2 of the rect of the stack, 
you'll know the height of the title bar.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

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  wrote:


And if you set "the effective rect" of the stack:

 set the effective rect of this stack to the working screenrect

..you get the placement you're looking for without having to know the 
OS-specific window trimming metrics.


Which version are you using?

Here's my results:

6.6.2 RC6: works as documented

6.7 DP4:   strange placement (Bug #12593)

7.0 DP6:   works as documented


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Terence Heaford]

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  wrote:

> And if you set "the effective rect" of the stack:
> 
>  set the effective rect of this stack to the working screenrect
> 
> ..you get the placement you're looking for without having to know the 
> OS-specific window trimming metrics.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

Terence Heaford wrote:

> On 3 Jun 2014, at 19:10, Richard Gaskin wrote:
>>
>> In all xTalks "the rect" of a stack refers only to its content
>> region.
...
>> LiveCode now does this for us with "the effective rect", which
>> accounts for the platform-specific window trimmings (title bar,
>> borders, etc.).
>
>
> 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 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 the Mac
> Menubar.
>
> If I change it to "set the rect of this stack to 0,44,1680,1046” then
> the traffic lights are positioned correctly below the Mac Menubar.

And if you set "the effective rect" of the stack:

  set the effective rect of this stack to the working screenrect

..you get the placement you're looking for without having to know the 
OS-specific window trimming metrics.


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Terence Heaford]

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
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 the Mac Menubar.

If I change it to "set the rect of this stack to 0,44,1680,1046” then the 
traffic lights are positioned correctly below the Mac Menubar.

All the best

Terry



On 3 Jun 2014, at 19:10, Richard Gaskin  wrote:

> LiveCode now does this for us with "the effective rect", which accounts for 
> the platform-specific window trimmings (title bar, borders, etc.).

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Richard Gaskin]

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 the correct co-ordinate for Mac and not rely
> on me converting a Windows co-ordinate?

Of course not.  It might be a bug, but before we go there we can notice 
that difference sounds suspiciously like the height of the Mac OS title bar.


In all xTalks "the rect" of a stack refers only to its content region.

In older xTalks (and older versions of LC) proper window placement 
required us to hard-wire values for the Mac title bar, and query the Win 
registry for that platform, and adjust accordingly.


LiveCode now does this for us with "the effective rect", which accounts 
for the platform-specific window trimmings (title bar, borders, etc.).


--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 Follow me on Twitter:  http://twitter.com/FourthWorldSys


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: ScreenRect bug or not

[Terence Heaford]

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 and not rely on me 
converting a Windows co-ordinate?

All the best

Terry


On 3 Jun 2014, at 18:38, Terence Heaford  wrote:

> 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 it should be otherwise:
> 
> "Adding the working adjective to either form returns the virtual co-ordinates 
> of each screen's working-area. The working-area of a screen is defined to be 
> the area not covered by OS furniture (such as the task bar on Windows, and 
> the Dock and Menubar on Mac OS X).”
> 
> Is this a bug or are the documents incorrect.
> 
> If the documents are incorrect then is there a LC function that returns the 
> height of the Mac menubar?
> 
> 
> 
> 
> All the best
> 
> Terry
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

ScreenRect bug or not

[Terence Heaford]

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 it should be otherwise:

"Adding the working adjective to either form returns the virtual co-ordinates 
of each screen's working-area. The working-area of a screen is defined to be 
the area not covered by OS furniture (such as the task bar on Windows, and the 
Dock and Menubar on Mac OS X).”

Is this a bug or are the documents incorrect.

If the documents are incorrect then is there a LC function that returns the 
height of the Mac menubar?




All the best

Terry
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iOS 4-Inch screenRect

[Dan Friedman]

Colin,

Thank you!  I knew that, and had the image in place...  but, in my stupidity, I 
moved the folder that contains the image and therefore was invalid.  Not sure 
why LC didn't warn me about the missing image?  Working now... THANKS!

-Dan

>> You have to include the 4 inch splash screen for it to then work in 4 inch 
>> mode.
> 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 flipped and didn't know it?  Is there a 
> reportWrongValues property I don't know about?
> 
> Hope someone knows the answer...
> 
> -Dan

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: iOS 4-Inch screenRect

[Colin Holgate]

You have to include the 4 inch splash screen for it to then work in 4 inch mode.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

iOS 4-Inch screenRect

[Dan Friedman]

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 flipped and didn't know it?  Is there a 
reportWrongValues property I don't know about?

Hope someone knows the answer...

-Dan
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: effective working screenRect

[Geoff Canyon]

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 scales pretty much the way I would expect, 50% (2.5x):

   repeat 200
  wait 2 ticks
   end repeat

And as you said, this pegs at 100%

   repeat 200
  wait 1 ticks
   end repeat


On Sat, Aug 10, 2013 at 4:01 PM, Mark Wieder  wrote:

> 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
>  mwie...@ahsoftware.net
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: 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
 mwie...@ahsoftware.net


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: effective working screenRect

[Geoff Canyon]

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.
>
> Not that odd. One tick is a pretty small time slice. Maybe
> wait 1 tick with messages
> might work better, but I can't imagine that tight a loop leading to
> anything but trouble.
>


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 agreed, although I don't know Dan's particular circumstances, changing
the wait command to 20 ticks seems perfectly reasonable.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: effective working screenRect

[Mark Wieder]

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 with messages
might work better, but I can't imagine that tight a loop leading to
anything but trouble.

-- 
-Mark Wieder
 mwie...@ahsoftware.net


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: effective working screenRect

[Geoff Canyon]

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 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 enough. Still, 
that's odd.

Sent from my iPad

On Aug 10, 2013, at 9:47 AM, Dan Friedman  wrote:

> 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.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: effective working screenRect

[Mark Wieder]

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 subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: effective working screenRect

[Dan Friedman]

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 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 way, same 
> new value, same new value? Or would it be same, same, a little different, a 
> little more different, still more different, mostly different, nearly done, 
> all done, all done, all done?
> 
> Sent from my iPad
>> 
>> On Aug 9, 2013, at 8:47 PM, Dan Friedman > 
>> 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", true
>> mobileControlDo "myTextField", "focus"
>> put the effective working screenRect into rRect
>> 
>> tRect is 0,0,320,480
>> rRect is also 0,0,320,480  (It should be the rect with the keyboard removed.)
>> 
>> I found that if I wait 20 ticks before I get the effective working 
>> screenRect again, it returns the correct value.
>> 
>> Anyone know the story on this?
>> 
>> 
>> Thanks in advance!
>> 
>> -Dan

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: effective working screenRect

[Geoff Canyon]

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 way, same new 
value, same new value? Or would it be same, same, a little different, a little 
more different, still more different, mostly different, nearly done, all done, 
all done, all done?

Sent from my iPad

On Aug 9, 2013, at 8:47 PM, Dan Friedman  wrote:

> 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", true
> mobileControlDo "myTextField", "focus"
> put the effective working screenRect into rRect
> 
> tRect is 0,0,320,480
> rRect is also 0,0,320,480  (It should be the rect with the keyboard removed.)
> 
> I found that if I wait 20 ticks before I get the effective working screenRect 
> again, it returns the correct value.
> 
> Anyone know the story on this?
> 
> 
> Thanks in advance!
> 
> -Dan
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

effective working screenRect

[Dan Friedman]

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", true
mobileControlDo "myTextField", "focus"
put the effective working screenRect into rRect

tRect is 0,0,320,480
rRect is also 0,0,320,480  (It should be the rect with the keyboard removed.)

I found that if I wait 20 ticks before I get the effective working screenRect 
again, it returns the correct value.

Anyone know the story on this?


Thanks in advance!

-Dan
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: IDE windows and screenrect

[Mark Schonewille]

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.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

Become our partner in sales http://qery.us/1bq Start selling Color Converter 
today. 20% commission!

On 24 dec 2011, at 16:27, Mike Bonner wrote:

> Ah k yep. Thats the one thanks very much!
> 


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: IDE windows and screenrect

[Mike Bonner]

Ah k yep. Thats the one thanks very much!

On Sat, Dec 24, 2011 at 8:15 AM, Mark Schonewille <
m.schonewi...@economy-x-talk.com> wrote:

> 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 http://clipboardlink.economy-x-talk.com
>
>
> Op 24 dec. 2011 om 16:08 heeft Mike Bonner  het
> volgende geschreven:
>
> > 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
> > against the screenrects.
> >
> > On this subject though, is there a message sent if a monitor in a dual
> > setup goes offline? (again, so that the windows can be re-arranged based
> on
> > the new configuration)
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: IDE windows and screenrect

[Mark Schonewille]

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 
http://clipboardlink.economy-x-talk.com


Op 24 dec. 2011 om 16:08 heeft Mike Bonner  het volgende 
geschreven:

> 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
> against the screenrects.
> 
> On this subject though, is there a message sent if a monitor in a dual
> setup goes offline? (again, so that the windows can be re-arranged based on
> the new configuration)
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode