subject:"Re\: Problems with Multiple Monitors"

Good catch, Gabe. my menubar is set to the bottom MBP display, and didn’t think 
to mess with the menubar in the top display.

Thanks,
Roger

> On May 6, 2021, at 12:10 PM, Gabe J via use-livecode 
>  wrote:
> 
> Oh, I think I see what the difference is: The screenRects will be in a
> different order depending on which screen the menubar is set to. So, when
> the menubar is set to the top screen, your script sends stack "revMenubar"
> to the bottom screen. I was running with the menubar set to be on the top
> screen. The solution would be to cycle through the working screenRects
> looking for the highest top.
> 
> Gabe
> 
> 
> On Thu, May 6, 2021 at 2:01 PM Gabe J  wrote:
> 
>> Yeah, "Displays have separate Spaces" is unchecked. Yes, your script is
>> moving stack "revMenubar" to near the top of the bottom screen when the top
>> and bottom screen are left-aligned, but since it is on the bottom screen
>> (below stacks on the top screen) the stacks above it on the top screen do
>> not work properly when manually moved. (LC 9.6.1 and macOS Catalina). The
>> solution is to just always move stack "revMenubar" to near the top of the
>> top screen.
>> 
>> Gabe
>> 
>> 
>> On Thu, May 6, 2021 at 1:52 PM Roger Guay via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>>> Huh . . . this is hard to understand since the script toggles revMenubar
>>> precisely to the top of one monitor or the other based on returned
>>> screenRects.
>>> 
>>> And, you unchecked the “Displays have separate Spaces” in the Mission
>>> Control System Prefs?
>>> 
>>> Roger
>>> 
 On May 6, 2021, at 11:39 AM, Gabe J via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
 
 However, I just tried your script and it looks like it isn't working. I
 have an external screen positioned above my laptop and it ran into the
>>> same
 problem: Since stack "revMenubar" is positioned lower than some of the
 stacks (when those stacks are on the top screen), the stacks will
>>> report as
 being below their visual position (when manually moved), or they just
>>> jump
 down to the bottom screen to be under stack "revMenubar" when I try to
 position them on the top screen. I'm using LC 9.6.1.
>>> 
>>> ___
>>> 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: Problems with Multiple Monitors

Oh, I think I see what the difference is: The screenRects will be in a
different order depending on which screen the menubar is set to. So, when
the menubar is set to the top screen, your script sends stack "revMenubar"
to the bottom screen. I was running with the menubar set to be on the top
screen. The solution would be to cycle through the working screenRects
looking for the highest top.

Gabe


On Thu, May 6, 2021 at 2:01 PM Gabe J  wrote:

> Yeah, "Displays have separate Spaces" is unchecked. Yes, your script is
> moving stack "revMenubar" to near the top of the bottom screen when the top
> and bottom screen are left-aligned, but since it is on the bottom screen
> (below stacks on the top screen) the stacks above it on the top screen do
> not work properly when manually moved. (LC 9.6.1 and macOS Catalina). The
> solution is to just always move stack "revMenubar" to near the top of the
> top screen.
>
> Gabe
>
>
> On Thu, May 6, 2021 at 1:52 PM Roger Guay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Huh . . . this is hard to understand since the script toggles revMenubar
>> precisely to the top of one monitor or the other based on returned
>> screenRects.
>>
>> And, you unchecked the “Displays have separate Spaces” in the Mission
>> Control System Prefs?
>>
>> Roger
>>
>> > On May 6, 2021, at 11:39 AM, Gabe J via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> > However, I just tried your script and it looks like it isn't working. I
>> > have an external screen positioned above my laptop and it ran into the
>> same
>> > problem: Since stack "revMenubar" is positioned lower than some of the
>> > stacks (when those stacks are on the top screen), the stacks will
>> report as
>> > being below their visual position (when manually moved), or they just
>> jump
>> > down to the bottom screen to be under stack "revMenubar" when I try to
>> > position them on the top screen. I'm using LC 9.6.1.
>>
>> ___
>> 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: Problems with Multiple Monitors

Yeah, "Displays have separate Spaces" is unchecked. Yes, your script is
moving stack "revMenubar" to near the top of the bottom screen when the top
and bottom screen are left-aligned, but since it is on the bottom screen
(below stacks on the top screen) the stacks above it on the top screen do
not work properly when manually moved. (LC 9.6.1 and macOS Catalina). The
solution is to just always move stack "revMenubar" to near the top of the
top screen.

Gabe


On Thu, May 6, 2021 at 1:52 PM Roger Guay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Huh . . . this is hard to understand since the script toggles revMenubar
> precisely to the top of one monitor or the other based on returned
> screenRects.
>
> And, you unchecked the “Displays have separate Spaces” in the Mission
> Control System Prefs?
>
> Roger
>
> > On May 6, 2021, at 11:39 AM, Gabe J via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > However, I just tried your script and it looks like it isn't working. I
> > have an external screen positioned above my laptop and it ran into the
> same
> > problem: Since stack "revMenubar" is positioned lower than some of the
> > stacks (when those stacks are on the top screen), the stacks will report
> as
> > being below their visual position (when manually moved), or they just
> jump
> > down to the bottom screen to be under stack "revMenubar" when I try to
> > position them on the top screen. I'm using LC 9.6.1.
>
> ___
> 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: Problems with Multiple Monitors

Huh . . . this is hard to understand since the script toggles revMenubar 
precisely to the top of one monitor or the other based on returned screenRects.

And, you unchecked the “Displays have separate Spaces” in the Mission Control 
System Prefs?

Roger

> On May 6, 2021, at 11:39 AM, Gabe J via use-livecode 
>  wrote:
> 
> However, I just tried your script and it looks like it isn't working. I
> have an external screen positioned above my laptop and it ran into the same
> problem: Since stack "revMenubar" is positioned lower than some of the
> stacks (when those stacks are on the top screen), the stacks will report as
> being below their visual position (when manually moved), or they just jump
> down to the bottom screen to be under stack "revMenubar" when I try to
> position them on the top screen. I'm using LC 9.6.1.

___
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: Problems with Multiple Monitors

If I were to do everything on the bottom screen, it would work. But to use
stacks on the top screen, stack "revMenubar" needs to go to the top of the
top screen, it appears. (At least in LC 9.6.1)

Gabe


On Thu, May 6, 2021 at 1:39 PM Gabe J  wrote:

> Sorry Roger,
>
> I was replying to the email thread--- I clicked reply on your message
> because it was the last one in my list here.
>
> However, I just tried your script and it looks like it isn't working. I
> have an external screen positioned above my laptop and it ran into the same
> problem: Since stack "revMenubar" is positioned lower than some of the
> stacks (when those stacks are on the top screen), the stacks will report as
> being below their visual position (when manually moved), or they just jump
> down to the bottom screen to be under stack "revMenubar" when I try to
> position them on the top screen. I'm using LC 9.6.1.
>
> Gabe
>
>
> On Thu, May 6, 2021 at 1:15 PM Roger Guay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Gabe, before delving deeply into your message, are you saying that my
>> script does not work for you?
>>
>> Roger
>>
>> > On May 6, 2021, at 9:56 AM, Gabe J via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> > Also, the point of my previous email is that stack "revMenubar" seems to
>> > move around sometimes when you change multi-monitor configurations on
>> Mac,
>> > which sets up the conditions for this issue.
>> >
>> > Gabe
>> >
>> > On Thu, May 6, 2021 at 11:52 AM Gabe J  wrote:
>> >
>> >> I've discovered that LiveCode (at least LC 9.6.1) seems to force the
>> >> reported top of a manually-moved stack to be the bottom of stack
>> >> "revMenubar" + 20, if the stack is overlapping revMenubar (even if
>> >> revMenubar is not visible), even if the visual top of the stack is
>> higher
>> >> than that. All mouse clicks will be vertically off by whatever offset
>> there
>> >> is between the bottom of stack "revMenubar" + 20 and the visual top of
>> the
>> >> overlapping, manually-moved stack.
>> >>
>> >> For example, if you were to run this:
>> >>
>> >>set the bottom of stack "revMenubar" to 200
>> >>
>> >> And then move a stack so that it overlaps revMenubar (manually moving
>> the
>> >> stack seems to possibly be a necessary step), if you run "put the top
>> of
>> >> ..." for that overlapping stack, it will be 220, even if it is visually
>> >> above 220, and mouse clicks in the stack will also be vertically off.
>> >>
>> >> If I set the position of stack "revMenubar" so that its bottom is above
>> >> the highest working screenRect's top + 20 (or whatever the height of
>> the
>> >> window's title bars are?), this issue can be avoided. I have made a
>> handler
>> >> which does this when the screenRects change.
>> >>
>> >> I ran into another potential bug where the bottom of a stack couldn't
>> be
>> >> positioned in a certain area without it also reporting the
>> top/mouseclicks
>> >> incorrectly on a second screen above my laptop's screen, but I haven't
>> >> figured out why that is, yet.
>> >>
>> >> Gabe
>> >>
>> >>
>> >> On Thu, May 6, 2021 at 9:58 AM Roger Guay via use-livecode <
>> >> use-livecode@lists.runrev.com> wrote:
>> >>
>> >>> Hi Fred et al,
>> >>>
>> >>> I use the following script to switch the monitor I wish to use for the
>> >>> revmenubar and revTools and then position pallets like my own rTools
>> and
>> >>> tmAlign3. It is working quite nicely for me with my external monitor
>> >>> positioned above my MBP and “Displays have separate spaces” unchecked.
>> >>>
>> >>>
>> >>> on mouseUp
>> >>>
>> >>> put the screenrects into tsr
>> >>>
>> >>>if the number of lines of tsr = 2 then
>> >>>
>> >>>if the left of stack revmenubar = item 1 of tsr then
>> >>>
>> >>>set the left of stack revmenubar to item 1 of
>> >>> line 2 of tsr
>> >>>
>> >>>set the top of stack revmenubar to item 2 of
>> line
>> >>> 2 of tsr + 25
>> >>>
>> >>>else
>> >>>
>> >>>set the left of stack revmenubar to item 1 of
>> tsr
>> >>>
>> >>>set the top of stack revmenubar to item 2 of
>> tsr
>> >>> + 25
>> >>>
>> >>>end if
>> >>>
>> >>>end if
>> >>>
>> >>>positionPalletes
>> >>>
>> >>>pass mouseUp
>> >>>
>> >>> end mouseUp
>> >>>
>> >>>
>> >>> on positionPalletes
>> >>>
>> >>>set the top of stack revtools to the bottom of stack
>> revMenuBar +
>> >>> 20
>> >>>
>> >>>set the left of stack revTools to the left of stack revmenubar
>> >>>
>> >>>set the top of stack rtools to the bottom of stack revMenuBar
>> + 20
>> >>>
>> >>>set the left of stack rTools to the right of stack revtools
>> >>>
>> >>>set the left of stack tmAlign3 to the right of stack revMenubar
>> >>>
>> >>>set the top of stack tmAlign3 to the top of stack revMenubar
>> >>>
>> >>> end positionPalletes
>> >>>
>> >>>
>> >>>
>> >>>

Re: Problems with Multiple Monitors

Sorry Roger,

I was replying to the email thread--- I clicked reply on your message
because it was the last one in my list here.

However, I just tried your script and it looks like it isn't working. I
have an external screen positioned above my laptop and it ran into the same
problem: Since stack "revMenubar" is positioned lower than some of the
stacks (when those stacks are on the top screen), the stacks will report as
being below their visual position (when manually moved), or they just jump
down to the bottom screen to be under stack "revMenubar" when I try to
position them on the top screen. I'm using LC 9.6.1.

Gabe


On Thu, May 6, 2021 at 1:15 PM Roger Guay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Gabe, before delving deeply into your message, are you saying that my
> script does not work for you?
>
> Roger
>
> > On May 6, 2021, at 9:56 AM, Gabe J via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Also, the point of my previous email is that stack "revMenubar" seems to
> > move around sometimes when you change multi-monitor configurations on
> Mac,
> > which sets up the conditions for this issue.
> >
> > Gabe
> >
> > On Thu, May 6, 2021 at 11:52 AM Gabe J  wrote:
> >
> >> I've discovered that LiveCode (at least LC 9.6.1) seems to force the
> >> reported top of a manually-moved stack to be the bottom of stack
> >> "revMenubar" + 20, if the stack is overlapping revMenubar (even if
> >> revMenubar is not visible), even if the visual top of the stack is
> higher
> >> than that. All mouse clicks will be vertically off by whatever offset
> there
> >> is between the bottom of stack "revMenubar" + 20 and the visual top of
> the
> >> overlapping, manually-moved stack.
> >>
> >> For example, if you were to run this:
> >>
> >>set the bottom of stack "revMenubar" to 200
> >>
> >> And then move a stack so that it overlaps revMenubar (manually moving
> the
> >> stack seems to possibly be a necessary step), if you run "put the top of
> >> ..." for that overlapping stack, it will be 220, even if it is visually
> >> above 220, and mouse clicks in the stack will also be vertically off.
> >>
> >> If I set the position of stack "revMenubar" so that its bottom is above
> >> the highest working screenRect's top + 20 (or whatever the height of the
> >> window's title bars are?), this issue can be avoided. I have made a
> handler
> >> which does this when the screenRects change.
> >>
> >> I ran into another potential bug where the bottom of a stack couldn't be
> >> positioned in a certain area without it also reporting the
> top/mouseclicks
> >> incorrectly on a second screen above my laptop's screen, but I haven't
> >> figured out why that is, yet.
> >>
> >> Gabe
> >>
> >>
> >> On Thu, May 6, 2021 at 9:58 AM Roger Guay via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >>> Hi Fred et al,
> >>>
> >>> I use the following script to switch the monitor I wish to use for the
> >>> revmenubar and revTools and then position pallets like my own rTools
> and
> >>> tmAlign3. It is working quite nicely for me with my external monitor
> >>> positioned above my MBP and “Displays have separate spaces” unchecked.
> >>>
> >>>
> >>> on mouseUp
> >>>
> >>> put the screenrects into tsr
> >>>
> >>>if the number of lines of tsr = 2 then
> >>>
> >>>if the left of stack revmenubar = item 1 of tsr then
> >>>
> >>>set the left of stack revmenubar to item 1 of
> >>> line 2 of tsr
> >>>
> >>>set the top of stack revmenubar to item 2 of
> line
> >>> 2 of tsr + 25
> >>>
> >>>else
> >>>
> >>>set the left of stack revmenubar to item 1 of
> tsr
> >>>
> >>>set the top of stack revmenubar to item 2 of tsr
> >>> + 25
> >>>
> >>>end if
> >>>
> >>>end if
> >>>
> >>>positionPalletes
> >>>
> >>>pass mouseUp
> >>>
> >>> end mouseUp
> >>>
> >>>
> >>> on positionPalletes
> >>>
> >>>set the top of stack revtools to the bottom of stack revMenuBar
> +
> >>> 20
> >>>
> >>>set the left of stack revTools to the left of stack revmenubar
> >>>
> >>>set the top of stack rtools to the bottom of stack revMenuBar +
> 20
> >>>
> >>>set the left of stack rTools to the right of stack revtools
> >>>
> >>>set the left of stack tmAlign3 to the right of stack revMenubar
> >>>
> >>>set the top of stack tmAlign3 to the top of stack revMenubar
> >>>
> >>> end positionPalletes
> >>>
> >>>
> >>>
> >>> HTH,
> >>> Roger
> >>>
> >>>
> >>>
>  On May 6, 2021, at 1:41 AM, Fred Moyer via use-livecode <
> >>> use-livecode@lists.runrev.com> wrote:
> 
> 
> 
> > On May 4, 2021, at 5:32 PM, Fred Moyer  wrote:
> >
> > Anyone having problems with multiple monitors and LC? I’m running
> >>> 9.6.1 - Mac. I have a feeling LC is confused because I like to connect
> and
> >>> disconnect monitors from

Re: Problems with Multiple Monitors

Gabe, before delving deeply into your message, are you saying that my script 
does not work for you?

Roger

> On May 6, 2021, at 9:56 AM, Gabe J via use-livecode 
>  wrote:
> 
> Also, the point of my previous email is that stack "revMenubar" seems to
> move around sometimes when you change multi-monitor configurations on Mac,
> which sets up the conditions for this issue.
> 
> Gabe
> 
> On Thu, May 6, 2021 at 11:52 AM Gabe J  wrote:
> 
>> I've discovered that LiveCode (at least LC 9.6.1) seems to force the
>> reported top of a manually-moved stack to be the bottom of stack
>> "revMenubar" + 20, if the stack is overlapping revMenubar (even if
>> revMenubar is not visible), even if the visual top of the stack is higher
>> than that. All mouse clicks will be vertically off by whatever offset there
>> is between the bottom of stack "revMenubar" + 20 and the visual top of the
>> overlapping, manually-moved stack.
>> 
>> For example, if you were to run this:
>> 
>>set the bottom of stack "revMenubar" to 200
>> 
>> And then move a stack so that it overlaps revMenubar (manually moving the
>> stack seems to possibly be a necessary step), if you run "put the top of
>> ..." for that overlapping stack, it will be 220, even if it is visually
>> above 220, and mouse clicks in the stack will also be vertically off.
>> 
>> If I set the position of stack "revMenubar" so that its bottom is above
>> the highest working screenRect's top + 20 (or whatever the height of the
>> window's title bars are?), this issue can be avoided. I have made a handler
>> which does this when the screenRects change.
>> 
>> I ran into another potential bug where the bottom of a stack couldn't be
>> positioned in a certain area without it also reporting the top/mouseclicks
>> incorrectly on a second screen above my laptop's screen, but I haven't
>> figured out why that is, yet.
>> 
>> Gabe
>> 
>> 
>> On Thu, May 6, 2021 at 9:58 AM Roger Guay via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>>> Hi Fred et al,
>>> 
>>> I use the following script to switch the monitor I wish to use for the
>>> revmenubar and revTools and then position pallets like my own rTools and
>>> tmAlign3. It is working quite nicely for me with my external monitor
>>> positioned above my MBP and “Displays have separate spaces” unchecked.
>>> 
>>> 
>>> on mouseUp
>>> 
>>> put the screenrects into tsr
>>> 
>>>if the number of lines of tsr = 2 then
>>> 
>>>if the left of stack revmenubar = item 1 of tsr then
>>> 
>>>set the left of stack revmenubar to item 1 of
>>> line 2 of tsr
>>> 
>>>set the top of stack revmenubar to item 2 of line
>>> 2 of tsr + 25
>>> 
>>>else
>>> 
>>>set the left of stack revmenubar to item 1 of tsr
>>> 
>>>set the top of stack revmenubar to item 2 of tsr
>>> + 25
>>> 
>>>end if
>>> 
>>>end if
>>> 
>>>positionPalletes
>>> 
>>>pass mouseUp
>>> 
>>> end mouseUp
>>> 
>>> 
>>> on positionPalletes
>>> 
>>>set the top of stack revtools to the bottom of stack revMenuBar +
>>> 20
>>> 
>>>set the left of stack revTools to the left of stack revmenubar
>>> 
>>>set the top of stack rtools to the bottom of stack revMenuBar + 20
>>> 
>>>set the left of stack rTools to the right of stack revtools
>>> 
>>>set the left of stack tmAlign3 to the right of stack revMenubar
>>> 
>>>set the top of stack tmAlign3 to the top of stack revMenubar
>>> 
>>> end positionPalletes
>>> 
>>> 
>>> 
>>> HTH,
>>> Roger
>>> 
>>> 
>>> 
 On May 6, 2021, at 1:41 AM, Fred Moyer via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
 
 
 
> On May 4, 2021, at 5:32 PM, Fred Moyer  wrote:
> 
> Anyone having problems with multiple monitors and LC? I’m running
>>> 9.6.1 - Mac. I have a feeling LC is confused because I like to connect and
>>> disconnect monitors from my MacBook Pro. (Even the MacOS sometimes gets
>>> confused.) But now LC is doing crazy things — even when no external
>>> monitors are connected. I’ll move the mouse to the top of a stack window,
>>> and ask for the Mouseloc and it will return something like "100,-60”. If I
>>> click a button in the middle of the stack, the click will register in an
>>> object the 60 pixels above that. It’s not always 60 — the wrongness changed
>>> as I move the stack around. Other times it works fine. I can’t find a
>>> pattern to set it off.
> 
> Any suggestions?
> Thanks.
> 
> Fred
> 
> 
 
 Thanks everyone for the interesting replies. I learned a lot
>>> (“desktopChanged", "the working screenrects,” difference between "the
>>> screenrect" and "the screenrects," etc.) I have a hunch, though, my problem
>>> may relate to stack RevMenubar and some accommodation the IDE makes for
>>> “the mouseV” depending on whether RevMenubar is showing or whether

Re: Problems with Multiple Monitors

Also, the point of my previous email is that stack "revMenubar" seems to
move around sometimes when you change multi-monitor configurations on Mac,
which sets up the conditions for this issue.

Gabe

On Thu, May 6, 2021 at 11:52 AM Gabe J  wrote:

> I've discovered that LiveCode (at least LC 9.6.1) seems to force the
> reported top of a manually-moved stack to be the bottom of stack
> "revMenubar" + 20, if the stack is overlapping revMenubar (even if
> revMenubar is not visible), even if the visual top of the stack is higher
> than that. All mouse clicks will be vertically off by whatever offset there
> is between the bottom of stack "revMenubar" + 20 and the visual top of the
> overlapping, manually-moved stack.
>
> For example, if you were to run this:
>
> set the bottom of stack "revMenubar" to 200
>
> And then move a stack so that it overlaps revMenubar (manually moving the
> stack seems to possibly be a necessary step), if you run "put the top of
> ..." for that overlapping stack, it will be 220, even if it is visually
> above 220, and mouse clicks in the stack will also be vertically off.
>
> If I set the position of stack "revMenubar" so that its bottom is above
> the highest working screenRect's top + 20 (or whatever the height of the
> window's title bars are?), this issue can be avoided. I have made a handler
> which does this when the screenRects change.
>
> I ran into another potential bug where the bottom of a stack couldn't be
> positioned in a certain area without it also reporting the top/mouseclicks
> incorrectly on a second screen above my laptop's screen, but I haven't
> figured out why that is, yet.
>
> Gabe
>
>
> On Thu, May 6, 2021 at 9:58 AM Roger Guay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Hi Fred et al,
>>
>> I use the following script to switch the monitor I wish to use for the
>> revmenubar and revTools and then position pallets like my own rTools and
>> tmAlign3. It is working quite nicely for me with my external monitor
>> positioned above my MBP and “Displays have separate spaces” unchecked.
>>
>>
>> on mouseUp
>>
>> put the screenrects into tsr
>>
>> if the number of lines of tsr = 2 then
>>
>> if the left of stack revmenubar = item 1 of tsr then
>>
>> set the left of stack revmenubar to item 1 of
>> line 2 of tsr
>>
>> set the top of stack revmenubar to item 2 of line
>> 2 of tsr + 25
>>
>> else
>>
>> set the left of stack revmenubar to item 1 of tsr
>>
>> set the top of stack revmenubar to item 2 of tsr
>> + 25
>>
>> end if
>>
>> end if
>>
>> positionPalletes
>>
>> pass mouseUp
>>
>> end mouseUp
>>
>>
>> on positionPalletes
>>
>> set the top of stack revtools to the bottom of stack revMenuBar +
>> 20
>>
>> set the left of stack revTools to the left of stack revmenubar
>>
>> set the top of stack rtools to the bottom of stack revMenuBar + 20
>>
>> set the left of stack rTools to the right of stack revtools
>>
>> set the left of stack tmAlign3 to the right of stack revMenubar
>>
>> set the top of stack tmAlign3 to the top of stack revMenubar
>>
>> end positionPalletes
>>
>>
>>
>> HTH,
>> Roger
>>
>>
>>
>> > On May 6, 2021, at 1:41 AM, Fred Moyer via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> >
>> >
>> >> On May 4, 2021, at 5:32 PM, Fred Moyer  wrote:
>> >>
>> >> Anyone having problems with multiple monitors and LC? I’m running
>> 9.6.1 - Mac. I have a feeling LC is confused because I like to connect and
>> disconnect monitors from my MacBook Pro. (Even the MacOS sometimes gets
>> confused.) But now LC is doing crazy things — even when no external
>> monitors are connected. I’ll move the mouse to the top of a stack window,
>> and ask for the Mouseloc and it will return something like "100,-60”. If I
>> click a button in the middle of the stack, the click will register in an
>> object the 60 pixels above that. It’s not always 60 — the wrongness changed
>> as I move the stack around. Other times it works fine. I can’t find a
>> pattern to set it off.
>> >>
>> >> Any suggestions?
>> >> Thanks.
>> >>
>> >> Fred
>> >>
>> >>
>> >
>> > Thanks everyone for the interesting replies. I learned a lot
>> (“desktopChanged", "the working screenrects,” difference between "the
>> screenrect" and "the screenrects," etc.) I have a hunch, though, my problem
>> may relate to stack RevMenubar and some accommodation the IDE makes for
>> “the mouseV” depending on whether RevMenubar is showing or whether you have
>> your own menubar or whether that screen has a menubar in it  —  I dunno.
>> I’ve never understood how this works. I notice sometimes, though, when I
>> turn on Toolbar Text, it shows up about 100 or 200 pixels down.
>> >
>> > Fred
>> > ___
>> > use-livecode mailing list
>> >

Re: Problems with Multiple Monitors

I've discovered that LiveCode (at least LC 9.6.1) seems to force the
reported top of a manually-moved stack to be the bottom of stack
"revMenubar" + 20, if the stack is overlapping revMenubar (even if
revMenubar is not visible), even if the visual top of the stack is higher
than that. All mouse clicks will be vertically off by whatever offset there
is between the bottom of stack "revMenubar" + 20 and the visual top of the
overlapping, manually-moved stack.

For example, if you were to run this:

set the bottom of stack "revMenubar" to 200

And then move a stack so that it overlaps revMenubar (manually moving the
stack seems to possibly be a necessary step), if you run "put the top of
..." for that overlapping stack, it will be 220, even if it is visually
above 220, and mouse clicks in the stack will also be vertically off.

If I set the position of stack "revMenubar" so that its bottom is above the
highest working screenRect's top + 20 (or whatever the height of the
window's title bars are?), this issue can be avoided. I have made a handler
which does this when the screenRects change.

I ran into another potential bug where the bottom of a stack couldn't be
positioned in a certain area without it also reporting the top/mouseclicks
incorrectly on a second screen above my laptop's screen, but I haven't
figured out why that is, yet.

Gabe


On Thu, May 6, 2021 at 9:58 AM Roger Guay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi Fred et al,
>
> I use the following script to switch the monitor I wish to use for the
> revmenubar and revTools and then position pallets like my own rTools and
> tmAlign3. It is working quite nicely for me with my external monitor
> positioned above my MBP and “Displays have separate spaces” unchecked.
>
>
> on mouseUp
>
> put the screenrects into tsr
>
> if the number of lines of tsr = 2 then
>
> if the left of stack revmenubar = item 1 of tsr then
>
> set the left of stack revmenubar to item 1 of line
> 2 of tsr
>
> set the top of stack revmenubar to item 2 of line
> 2 of tsr + 25
>
> else
>
> set the left of stack revmenubar to item 1 of tsr
>
> set the top of stack revmenubar to item 2 of tsr +
> 25
>
> end if
>
> end if
>
> positionPalletes
>
> pass mouseUp
>
> end mouseUp
>
>
> on positionPalletes
>
> set the top of stack revtools to the bottom of stack revMenuBar +
> 20
>
> set the left of stack revTools to the left of stack revmenubar
>
> set the top of stack rtools to the bottom of stack revMenuBar + 20
>
> set the left of stack rTools to the right of stack revtools
>
> set the left of stack tmAlign3 to the right of stack revMenubar
>
> set the top of stack tmAlign3 to the top of stack revMenubar
>
> end positionPalletes
>
>
>
> HTH,
> Roger
>
>
>
> > On May 6, 2021, at 1:41 AM, Fred Moyer via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> >
> >
> >> On May 4, 2021, at 5:32 PM, Fred Moyer  wrote:
> >>
> >> Anyone having problems with multiple monitors and LC? I’m running 9.6.1
> - Mac. I have a feeling LC is confused because I like to connect and
> disconnect monitors from my MacBook Pro. (Even the MacOS sometimes gets
> confused.) But now LC is doing crazy things — even when no external
> monitors are connected. I’ll move the mouse to the top of a stack window,
> and ask for the Mouseloc and it will return something like "100,-60”. If I
> click a button in the middle of the stack, the click will register in an
> object the 60 pixels above that. It’s not always 60 — the wrongness changed
> as I move the stack around. Other times it works fine. I can’t find a
> pattern to set it off.
> >>
> >> Any suggestions?
> >> Thanks.
> >>
> >> Fred
> >>
> >>
> >
> > Thanks everyone for the interesting replies. I learned a lot
> (“desktopChanged", "the working screenrects,” difference between "the
> screenrect" and "the screenrects," etc.) I have a hunch, though, my problem
> may relate to stack RevMenubar and some accommodation the IDE makes for
> “the mouseV” depending on whether RevMenubar is showing or whether you have
> your own menubar or whether that screen has a menubar in it  —  I dunno.
> I’ve never understood how this works. I notice sometimes, though, when I
> turn on Toolbar Text, it shows up about 100 or 200 pixels down.
> >
> > Fred
> > ___
> > 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:
>

Re: Problems with Multiple Monitors

Hi Fred et al,

I use the following script to switch the monitor I wish to use for the 
revmenubar and revTools and then position pallets like my own rTools and 
tmAlign3. It is working quite nicely for me with my external monitor positioned 
above my MBP and “Displays have separate spaces” unchecked.


on mouseUp

put the screenrects into tsr

if the number of lines of tsr = 2 then

if the left of stack revmenubar = item 1 of tsr then

set the left of stack revmenubar to item 1 of line 2 of 
tsr

set the top of stack revmenubar to item 2 of line 2 of 
tsr + 25

else

set the left of stack revmenubar to item 1 of tsr

set the top of stack revmenubar to item 2 of tsr + 25

end if

end if

positionPalletes

pass mouseUp

end mouseUp


on positionPalletes

set the top of stack revtools to the bottom of stack revMenuBar + 20

set the left of stack revTools to the left of stack revmenubar

set the top of stack rtools to the bottom of stack revMenuBar + 20

set the left of stack rTools to the right of stack revtools

set the left of stack tmAlign3 to the right of stack revMenubar

set the top of stack tmAlign3 to the top of stack revMenubar

end positionPalletes



HTH,
Roger



> On May 6, 2021, at 1:41 AM, Fred Moyer via use-livecode 
>  wrote:
> 
> 
> 
>> On May 4, 2021, at 5:32 PM, Fred Moyer  wrote:
>> 
>> Anyone having problems with multiple monitors and LC? I’m running 9.6.1 - 
>> Mac. I have a feeling LC is confused because I like to connect and 
>> disconnect monitors from my MacBook Pro. (Even the MacOS sometimes gets 
>> confused.) But now LC is doing crazy things — even when no external monitors 
>> are connected. I’ll move the mouse to the top of a stack window, and ask for 
>> the Mouseloc and it will return something like "100,-60”. If I click a 
>> button in the middle of the stack, the click will register in an object the 
>> 60 pixels above that. It’s not always 60 — the wrongness changed as I move 
>> the stack around. Other times it works fine. I can’t find a pattern to set 
>> it off.
>> 
>> Any suggestions?
>> Thanks.
>> 
>> Fred
>> 
>> 
> 
> Thanks everyone for the interesting replies. I learned a lot 
> (“desktopChanged", "the working screenrects,” difference between "the 
> screenrect" and "the screenrects," etc.) I have a hunch, though, my problem 
> may relate to stack RevMenubar and some accommodation the IDE makes for “the 
> mouseV” depending on whether RevMenubar is showing or whether you have your 
> own menubar or whether that screen has a menubar in it  —  I dunno. I’ve 
> never understood how this works. I notice sometimes, though, when I turn on 
> Toolbar Text, it shows up about 100 or 200 pixels down.
> 
> Fred
> ___
> 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: Problems with Multiple Monitors

2021-05-06 Thread Paul Dupuis via use-livecode

On 5/6/2021 4:41 AM, Fred Moyer via use-livecode wrote:

On May 4, 2021, at 5:32 PM, Fred Moyer wrote:

Anyone having problems with multiple monitors and LC? I’m running 9.6.1 - Mac. I
have a feeling LC is confused because I like to connect and disconnect monitors from
my MacBook Pro. (Even the MacOS sometimes gets confused.) But now LC is doing crazy
things — even when no external monitors are connected. I’ll move the mouse to the
top of a stack window, and ask for the Mouseloc and it will return something like
"100,-60”. If I click a button in the middle of the stack, the click will
register in an object the 60 pixels above that. It’s not always 60 — the wrongness
changed as I move the stack around. Other times it works fine. I can’t find a
pattern to set it off.

Any suggestions?
Thanks.

Fred

Thanks everyone for the interesting replies. I learned a lot (“desktopChanged", "the working
screenrects,” difference between "the screenrect" and "the screenrects," etc.) I have a
hunch, though, my problem may relate to stack RevMenubar and some accommodation the IDE makes for “the
mouseV” depending on whether RevMenubar is showing or whether you have your own menubar or whether that
screen has a menubar in it — I dunno. I’ve never understood how this works. I notice sometimes, though,
when I turn on Toolbar Text, it shows up about 100 or 200 pixels down.

Fred
___

You might also look in the dictionary at the windowBoundingRect property
- I think it only controls that are that windows van be maximized to,
but I forget the details. It is yet another screen area related
property. I am also not sure that windowBoundingRect is multipel monitor
aware as there is no "windowBoundingRects" (plural) version.

___
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: Problems with Multiple Monitors

2021-05-06 Thread Fred Moyer via use-livecode

> On May 4, 2021, at 5:32 PM, Fred Moyer  wrote:
> 
> Anyone having problems with multiple monitors and LC? I’m running 9.6.1 - 
> Mac. I have a feeling LC is confused because I like to connect and disconnect 
> monitors from my MacBook Pro. (Even the MacOS sometimes gets confused.) But 
> now LC is doing crazy things — even when no external monitors are connected. 
> I’ll move the mouse to the top of a stack window, and ask for the Mouseloc 
> and it will return something like "100,-60”. If I click a button in the 
> middle of the stack, the click will register in an object the 60 pixels above 
> that. It’s not always 60 — the wrongness changed as I move the stack around. 
> Other times it works fine. I can’t find a pattern to set it off.
> 
> Any suggestions?
> Thanks.
> 
> Fred
> 
> 

Thanks everyone for the interesting replies. I learned a lot (“desktopChanged", 
"the working screenrects,” difference between "the screenrect" and "the 
screenrects," etc.) I have a hunch, though, my problem may relate to stack 
RevMenubar and some accommodation the IDE makes for “the mouseV” depending on 
whether RevMenubar is showing or whether you have your own menubar or whether 
that screen has a menubar in it  —  I dunno. I’ve never understood how this 
works. I notice sometimes, though, when I turn on Toolbar Text, it shows up 
about 100 or 200 pixels down.

Fred
___
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: Problems with Multiple Monitors


On 5/5/2021 12:15 PM, Mark Wieder via use-livecode wrote:

On 5/5/21 8:53 AM, Paul Dupuis via use-livecode wrote:

I'm afraid I can't help with this. A good while ago, I moved to my 
own centerWindow command that doesn't use screenLoc, but uses the 
stack's (window's the screen property 9for the line number of the 
screenRect the stack is on) and the screenRects to get the rect of 
the monitor the window is on. I then use that monitor's rect to get 
the center coordinates and then adjust for any menubar or taskbar, 
etc to get the effective center for that monitor to center a window 
(I think I actually now use the working screenRects or effective 
screenRects or maybe the effective working screenRects ;-)


Yep - that's what I do as well.
A couple of useful enhancements would be

the screenLocs # return a list
the screenLoc(2) # allow a parameter for the screen number



I'd also like to see 'effective' and 'working' applied to the screenRect 
and screenRects and screenRect(the screen of window X)



___
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: Problems with Multiple Monitors


On 5/5/2021 12:15 PM, Mark Wieder via use-livecode wrote:

On 5/5/21 8:53 AM, Paul Dupuis via use-livecode wrote:

I'm afraid I can't help with this. A good while ago, I moved to my 
own centerWindow command that doesn't use screenLoc, but uses the 
stack's (window's the screen property 9for the line number of the 
screenRect the stack is on) and the screenRects to get the rect of 
the monitor the window is on. I then use that monitor's rect to get 
the center coordinates and then adjust for any menubar or taskbar, 
etc to get the effective center for that monitor to center a window 
(I think I actually now use the working screenRects or effective 
screenRects or maybe the effective working screenRects ;-)


Yep - that's what I do as well.
A couple of useful enhancements would be

the screenLocs # return a list
the screenLoc(2) # allow a parameter for the screen number



+1 to both of those!

___
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: Problems with Multiple Monitors

2021-05-05 Thread Mark Wieder via use-livecode


On 5/5/21 8:53 AM, Paul Dupuis via use-livecode wrote:

I'm afraid I can't help with this. A good while ago, I moved to my own 
centerWindow command that doesn't use screenLoc, but uses the stack's 
(window's the screen property 9for the line number of the screenRect the 
stack is on) and the screenRects to get the rect of the monitor the 
window is on. I then use that monitor's rect to get the center 
coordinates and then adjust for any menubar or taskbar, etc to get the 
effective center for that monitor to center a window (I think I actually 
now use the working screenRects or effective screenRects or maybe the 
effective working screenRects ;-)


Yep - that's what I do as well.
A couple of useful enhancements would be

the screenLocs # return a list
the screenLoc(2) # allow a parameter for the screen number

--
 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: Problems with Multiple Monitors


On 5/5/2021 11:42 AM, Richard Gaskin via use-livecode wrote:

Thanks, Paul, and the others who chimed in.

I'm familiar with the documented features for screen metrics, just 
trying to determine if the rect of the main screen no longer being the 
reference point for metrics is a change/bug I need to be concerned about?


And this got me thinking about screenLoc: if the main screen isn't the 
reference point, then is the screenLoc adjusted for the non-0,0 corner 
or is it based on the sum boundary of all connected monitors?


And is any of this platform-specific?

Or different from how it's been since the plural screenRects was 
introduced?




I'm afraid I can't help with this. A good while ago, I moved to my own 
centerWindow command that doesn't use screenLoc, but uses the stack's 
(window's the screen property 9for the line number of the screenRect the 
stack is on) and the screenRects to get the rect of the monitor the 
window is on. I then use that monitor's rect to get the center 
coordinates and then adjust for any menubar or taskbar, etc to get the 
effective center for that monitor to center a window (I think I actually 
now use the working screenRects or effective screenRects or maybe the 
effective working screenRects ;-)



___
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: Problems with Multiple Monitors

2021-05-05 Thread Richard Gaskin via use-livecode


Thanks, Paul, and the others who chimed in.

I'm familiar with the documented features for screen metrics, just 
trying to determine if the rect of the main screen no longer being the 
reference point for metrics is a change/bug I need to be concerned about?


And this got me thinking about screenLoc: if the main screen isn't the 
reference point, then is the screenLoc adjusted for the non-0,0 corner 
or is it based on the sum boundary of all connected monitors?


And is any of this platform-specific?

Or different from how it's been since the plural screenRects was introduced?

--
 Richard Gaskin
 Fourth World Systems


Paul Dupuis wrote:

On 5/4/2021 8:20 PM, Richard Gaskin via use-livecode wrote:

Paul Dupuis wrote:


With multiple monitor, zero vertical is the top of the top most
monitor  - regardless of whether it is the primary monitor or not.


If the screenRect is no longer based on the main monitor, what is the 
screenloc?


In a multi-monitor setup, with metrics like that how can one be 
expected to center a window?




screenRect still returns the rect of the main monitor
and
the first line of the screenRects is still the rect of the main or 
primary monitor (the one with the menubar/taskbar)


however, you can not count on its left,top of the primary monitor being 
0,0 in a multiple monitor configuration. It may be or it may not be 
depending of where the second (or more) monitors are in relation to the 
primary one. Took me a while to figure this one out based on a 
customer's reported symptoms!


Also, if you think you may have customers with multiple monitors, the on 
desktopChanged message is your friend. I ran into a customer who would 
often leave HyperRESEARCH running, minimized or hidden, and then remove 
a external monitor from their laptop to go. LiveCode still thinks the 
monitor is attached and when they placed HR windows on that external 
monitor, those windows were no visible or accessible (unless they quit 
and restarted HR). Now I have a desktopChanged handler that gets the 
screenRects and checks to see if every open window is inside a current 
screenRect and moves the windows if needed.


___
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: Problems with Multiple Monitors