Re: Problems with Multiple Monitors

[Roger Guay via use-livecode]

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

[Gabe J via use-livecode]

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

[Gabe J via use-livecode]

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

[Roger Guay via use-livecode]

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

[Gabe J via use-livecode]

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

[Gabe J via use-livecode]

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 m

Re: Problems with Multiple Monitors

[Roger Guay via use-livecode]

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

[Gabe J via use-livecode]

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

Re: Problems with Multiple Monitors

[Gabe J via use-livecode]

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:
> http://lists.runre

Re: notarizing DMG fails - solved

[Jim Lambert via use-livecode]

> 
> Thank you Matthias! Your tools make my life SO much easier! You have
> done a great service for this community.

+100

___
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

[Roger Guay via use-livecode]

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

[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

AW: which entity has to be notarized/stapled?

[Tiemo via use-livecode]

Hi Matthias,

your doc is wonderful helpful!
Just the matter is pretty complex for the first time, and there are quite a 
bunch of different approaches to go and I have to find the pieces for my 
approach. Therefore I wouldn't chop it into several docs.

Sometimes I overread some implicit informations you gave, like in this 
sentence: "To get our DMG and  the containing pkg or app  notarized by Apple we 
need to upload it to Apple."

For me it would be sometimes easier to read with some explicit informations, 
like:
" When you notarize a DMG, pkg, or bundle, everything inside is automatically 
unpacked and notarized as well. So you only need to upload the "top level" file 
for notarizing in a single pass, not the contents separately.
DMGs are like zip files -- notarization is not required to open them. However, 
their contents must be notarized in order to run. You can do one of two 
approaches:
Sign the app, put it in the DMG, sign the DMG, then upload the dmg to be 
notarized.
Zip up the app and notarize the app separately, then put it in a DMG and 
distribute the DMG without notarizing it" 

Which could be put at the beginning of chapter 7.

Or your explanation from your last post: " Stapling always staples the app, 
regardless if it is nested in one  container or more. When you send your app as 
 pkg, dmg or as pkg on dmg to apple, then you can staple those containers, 
because the stapling goes "through" and the stapling information is written to 
the .app inside the container."

Which could be added to chapter 7.5.

Your guide is perfect to go thru step by step, but I also want to understand, 
whats going on behind the scenes to know why I am doing what and what not.
But this is just my preference.

My 2 cents
Tiemo


-Ursprüngliche Nachricht-
Von: use-livecode  Im Auftrag von 
matthias rebbe via use-livecode
Gesendet: Donnerstag, 6. Mai 2021 11:42
An: How to use LiveCode 
Cc: matthias_livecode_150...@m-r-d.de
Betreff: Re: which entity has to be notarized/stapled?

Tiemo,

i am wondering, if my lesson is not clear enough about this. What do you think?

I really thought, that it's clear that you just have to sent only the top level 
container to Apple and that the local stapling process goes through the 
container and writes the information to the app within the container.

Or is the lesson just to complex and i should divide it in multiple parts to 
make it easier to understand?

Matthias



> Am 06.05.2021 um 11:19 schrieb Tiemo via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> I found an answer to my question here 
> https://developer.apple.com/forums/thread/650288 
>  :
> 
> You will need to sign the .pkg installer with Developer ID and notarize it in 
> order for it to install on macOS 10.14.5 and newer. The reason why it may 
> have appeared to work locally was that the pkg wasn't quarantined.
> 
> The recommended QA procedure for installation is to start with a fresh macOS 
> VM instance and use Air Drop or a web browser to download the file into it. 
> Then double click on it like a user would. If it installs and runs properly, 
> you can ship it.
> 
> DMGs are like zip files -- notarization is not required to open them. 
> However, their contents must be notarized in order to run. You can do one of 
> two approaches:
> 
> Sign the app, put it in the DMG, sign the DMG, then upload the dmg to be 
> notarized.
> 
> Zip up the app and notarize the app separately, then put it in a 
> DMG and distribute the DMG without notarizing it
> 
> When you notarize a DMG, pkg, or bundle, everything inside is automatically 
> unpacked and notarized as well. So you only need to upload the "top level" 
> file for notarizing in a single pass, not the contents separately.
> 
> You can read a lot more here: 
> https://developer.apple.com/documentation/xcode/notarizing_macos_softw
> are_before_distribution 
>  ware_before_distribution>
> 
> Tiemo
> 
> 
> -Ursprüngliche Nachricht-
> Von: use-livecode  > Im Auftrag von Tiemo 
> via use-livecode
> Gesendet: Donnerstag, 6. Mai 2021 10:28
> An: 'How to use LiveCode'  >
> Cc: toolb...@kestner.de 
> Betreff: which entity has to be notarized/stapled?
> 
> One question is left for me about notarization and stapling. If you have an 
> app, which is packaged and the package is wrapped in a DMG, which instance 
> should be notarized and which stapled? All three, each one after the other, 
> before proceeding to the next step, or only the outer shell, in this case the 
> DMG?
> 
> Is the notarization/stapeling checked by the gatekeeper only once at 
> installation time or at each start of the app?
> If I would only notarize and staple the outer DMG, is the notarization and 
> stapling be automatically issued d

Re: which entity has to be notarized/stapled?

[matthias rebbe via use-livecode]

Tiemo,

i am wondering, if my lesson is not clear enough about this. What do you think?

I really thought, that it's clear that you just have to sent only the top level 
container to Apple and that the local stapling process goes through the 
container and writes the information to the app within the container.

Or is the lesson just to complex and i should divide it in multiple parts to 
make it easier to understand?

Matthias



> Am 06.05.2021 um 11:19 schrieb Tiemo via use-livecode 
> mailto:use-livecode@lists.runrev.com>>:
> 
> I found an answer to my question here 
> https://developer.apple.com/forums/thread/650288 
>  :
> 
> You will need to sign the .pkg installer with Developer ID and notarize it in 
> order for it to install on macOS 10.14.5 and newer. The reason why it may 
> have appeared to work locally was that the pkg wasn't quarantined.
> 
> The recommended QA procedure for installation is to start with a fresh macOS 
> VM instance and use Air Drop or a web browser to download the file into it. 
> Then double click on it like a user would. If it installs and runs properly, 
> you can ship it.
> 
> DMGs are like zip files -- notarization is not required to open them. 
> However, their contents must be notarized in order to run. You can do one of 
> two approaches:
> 
> Sign the app, put it in the DMG, sign the DMG, then upload the dmg to be 
> notarized.
> 
> Zip up the app and notarize the app separately, then put it in a DMG and 
> distribute the DMG without notarizing it
> 
> When you notarize a DMG, pkg, or bundle, everything inside is automatically 
> unpacked and notarized as well. So you only need to upload the "top level" 
> file for notarizing in a single pass, not the contents separately.
> 
> You can read a lot more here: 
> https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution
>  
> 
> 
> Tiemo
> 
> 
> -Ursprüngliche Nachricht-
> Von: use-livecode  > Im Auftrag von Tiemo via 
> use-livecode
> Gesendet: Donnerstag, 6. Mai 2021 10:28
> An: 'How to use LiveCode'  >
> Cc: toolb...@kestner.de 
> Betreff: which entity has to be notarized/stapled?
> 
> One question is left for me about notarization and stapling. If you have an 
> app, which is packaged and the package is wrapped in a DMG, which instance 
> should be notarized and which stapled? All three, each one after the other, 
> before proceeding to the next step, or only the outer shell, in this case the 
> DMG?
> 
> Is the notarization/stapeling checked by the gatekeeper only once at 
> installation time or at each start of the app?
> If I would only notarize and staple the outer DMG, is the notarization and 
> stapling be automatically issued downwards to the content of the DMG down to 
> the package and the app inside the package? Or on the other hand, would it 
> interfere the process, if I would do notarization and stapling at each step?
> 
> Thanks for getting some insight in gatekeepers behaviour.
> 
> @Matthias: perhaps you want to add this information also in you doc in 
> chapter 7 / 7.5 to clarify this question?
> 
> Thanks
> Tiemo
> 
> -Ursprüngliche Nachricht-
> Von: use-livecode  > Im Auftrag von matthias rebbe 
> via use-livecode
> Gesendet: Donnerstag, 6. Mai 2021 01:18
> An: How to use LiveCode  >
> Cc: matthias_livecode_150...@m-r-d.de 
> 
> Betreff: Re: notarizing DMG fails - solved
> 
> Thanks Phil.
> 
> 
> @all
> I've updated the lesson at
> 
> https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore
>  
> 
> 
> now and added detailed information about package installers. 
> So it now contains also information about how to create,sign and notarize 
> package installers or package installers on dmg.
> 
> 
> It would be really awesome, if someone could check it. I needed to insert 
> some additional steps and i really hope that i did not forget to adjust some 
> references to internal steps.
> 
> So please let me if you find any errors, typos or wrong information.
> 
> Thanks.
> 
> Matthias
> 
> 
>> Am 05.05.2021 um 19:49 schrieb Phil Davis via use-livecode 
>> mailto:use-livecode@lists.runrev.com>>:
>> 
>> Thank you Matthias! Your tools make my life SO much easier! You have 
>> done a great service for this community.
>> 
>> Phil Davis
>> 
>> 
>> On 5/5/21 2:20 AM, matthias rebbe via use-livecode wrote:
 Am 05.05.2021 um 11:10 schrieb Tiemo via use-livecode 
>>

AW: which entity has to be notarized/stapled?

[Tiemo via use-livecode]

I found an answer to my question here 
https://developer.apple.com/forums/thread/650288 :

You will need to sign the .pkg installer with Developer ID and notarize it in 
order for it to install on macOS 10.14.5 and newer. The reason why it may have 
appeared to work locally was that the pkg wasn't quarantined.

The recommended QA procedure for installation is to start with a fresh macOS VM 
instance and use Air Drop or a web browser to download the file into it. Then 
double click on it like a user would. If it installs and runs properly, you can 
ship it.

DMGs are like zip files -- notarization is not required to open them. However, 
their contents must be notarized in order to run. You can do one of two 
approaches:

 Sign the app, put it in the DMG, sign the DMG, then upload the dmg to be 
notarized.

 Zip up the app and notarize the app separately, then put it in a DMG and 
distribute the DMG without notarizing it

When you notarize a DMG, pkg, or bundle, everything inside is automatically 
unpacked and notarized as well. So you only need to upload the "top level" file 
for notarizing in a single pass, not the contents separately.

You can read a lot more here: 
https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution

Tiemo


-Ursprüngliche Nachricht-
Von: use-livecode  Im Auftrag von Tiemo 
via use-livecode
Gesendet: Donnerstag, 6. Mai 2021 10:28
An: 'How to use LiveCode' 
Cc: toolb...@kestner.de
Betreff: which entity has to be notarized/stapled?

One question is left for me about notarization and stapling. If you have an 
app, which is packaged and the package is wrapped in a DMG, which instance 
should be notarized and which stapled? All three, each one after the other, 
before proceeding to the next step, or only the outer shell, in this case the 
DMG?

Is the notarization/stapeling checked by the gatekeeper only once at 
installation time or at each start of the app?
If I would only notarize and staple the outer DMG, is the notarization and 
stapling be automatically issued downwards to the content of the DMG down to 
the package and the app inside the package? Or on the other hand, would it 
interfere the process, if I would do notarization and stapling at each step?

Thanks for getting some insight in gatekeepers behaviour.

@Matthias: perhaps you want to add this information also in you doc in chapter 
7 / 7.5 to clarify this question?

Thanks
Tiemo

-Ursprüngliche Nachricht-
Von: use-livecode  Im Auftrag von 
matthias rebbe via use-livecode
Gesendet: Donnerstag, 6. Mai 2021 01:18
An: How to use LiveCode 
Cc: matthias_livecode_150...@m-r-d.de
Betreff: Re: notarizing DMG fails - solved

Thanks Phil.


@all
I've updated the lesson at

https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore

now and added detailed information about package installers. 
So it now contains also information about how to create,sign and notarize 
package installers or package installers on dmg.


It would be really awesome, if someone could check it. I needed to insert some 
additional steps and i really hope that i did not forget to adjust some 
references to internal steps.

So please let me if you find any errors, typos or wrong information.

Thanks.

Matthias


> Am 05.05.2021 um 19:49 schrieb Phil Davis via use-livecode 
> :
> 
> Thank you Matthias! Your tools make my life SO much easier! You have 
> done a great service for this community.
> 
> Phil Davis
> 
> 
> On 5/5/21 2:20 AM, matthias rebbe via use-livecode wrote:
>>> Am 05.05.2021 um 11:10 schrieb Tiemo via use-livecode 
>>> :
>>> 
>>> Thank you all for helping my lost soul in Apples notarizing nirvana
>>> 
>>> Tiemo
>>> 
>>> P.S.
>>> Matthias, perhaps you want to add this in your great helpfile - without 
>>> that it would have taken weeks for me!
>>> 
>> I am currently working on it. ;)
>> First i will just add a note, but later, when i have more free time  i will 
>> enhance it to describe all more detailed.
>> 
>> The Helper Stack will also get an update to support package installers. But 
>> it takes some time.
>> 
>> 
>> 
>>> -Ursprüngliche Nachricht-
>>> Von: use-livecode  Im Auftrag 
>>> von matthias rebbe via use-livecode
>>> Gesendet: Mittwoch, 5. Mai 2021 10:31
>>> An: How to use LiveCode 
>>> Cc: matthias_livecode_150...@m-r-d.de
>>> Betreff: Re: notarizing DMG fails
>>> 
>>> Tiemo,
>>> 
>>> i think i found the solution. I tried here myself and did als get the error 
>>> "this identity cannot be used for signing code" when using the Developer ID 
>>> Installer certificate for signing the .pkg.
>>> According to Apple (see point 2)
>>> https://help.apple.com/xcode/mac/current/#/deve51ce7c3d
>>> 
>>> you have to use the tool productsign to sign the package installer. 
>>> 
>>> So the syntax is like this
>>> 
>>> productsign --sign   
>>> 
>>> 
>>> Example
>>> productsign --sign "Developer ID Installe

Re: which entity has to be notarized/stapled?

[matthias rebbe via use-livecode]

So...

Stapling always staples the app, regardless if it is nested in one  container 
or more.

When you send your app as  pkg, dmg or as pkg on dmg to apple, then you can 
staple those containers, because the stapling goes "through" and the stapling 
information is written to the .app inside the container.

When you sent a .zip file to Apple, then you have to staple the .app itself. 
You do not need to extract the zip and staple that .app. You can staple the app 
from which you've created the .zip. The .zip file can be deleted, because it is 
not needed anymore.




-
Matthias Rebbe
Life Is Too Short For Boring Code

> Am 06.05.2021 um 10:28 schrieb Tiemo via use-livecode 
> :
> 
> One question is left for me about notarization and stapling. If you have an 
> app, which is packaged and the package is wrapped in a DMG, which instance 
> should be notarized and which stapled? All three, each one after the other, 
> before proceeding to the next step, or only the outer shell, in this case the 
> DMG?
> 
> Is the notarization/stapeling checked by the gatekeeper only once at 
> installation time or at each start of the app?
> If I would only notarize and staple the outer DMG, is the notarization and 
> stapling be automatically issued downwards to the content of the DMG down to 
> the package and the app inside the package? Or on the other hand, would it 
> interfere the process, if I would do notarization and stapling at each step?
> 
> Thanks for getting some insight in gatekeepers behaviour.
> 
> @Matthias: perhaps you want to add this information also in you doc in 
> chapter 7 / 7.5 to clarify this question?
> 
> Thanks
> Tiemo
> 
> -Ursprüngliche Nachricht-
> Von: use-livecode  Im Auftrag von 
> matthias rebbe via use-livecode
> Gesendet: Donnerstag, 6. Mai 2021 01:18
> An: How to use LiveCode 
> Cc: matthias_livecode_150...@m-r-d.de
> Betreff: Re: notarizing DMG fails - solved
> 
> Thanks Phil.
> 
> 
> @all
> I've updated the lesson at
> 
> https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore
> 
> now and added detailed information about package installers. 
> So it now contains also information about how to create,sign and notarize 
> package installers or package installers on dmg.
> 
> 
> It would be really awesome, if someone could check it. I needed to insert 
> some additional steps and i really hope that i did not forget to adjust some 
> references to internal steps.
> 
> So please let me if you find any errors, typos or wrong information.
> 
> Thanks.
> 
> Matthias
> 
> 
>> Am 05.05.2021 um 19:49 schrieb Phil Davis via use-livecode 
>> :
>> 
>> Thank you Matthias! Your tools make my life SO much easier! You have 
>> done a great service for this community.
>> 
>> Phil Davis
>> 
>> 
>> On 5/5/21 2:20 AM, matthias rebbe via use-livecode wrote:
 Am 05.05.2021 um 11:10 schrieb Tiemo via use-livecode 
 :
 
 Thank you all for helping my lost soul in Apples notarizing nirvana
 
 Tiemo
 
 P.S.
 Matthias, perhaps you want to add this in your great helpfile - without 
 that it would have taken weeks for me!
 
>>> I am currently working on it. ;)
>>> First i will just add a note, but later, when i have more free time  i will 
>>> enhance it to describe all more detailed.
>>> 
>>> The Helper Stack will also get an update to support package installers. But 
>>> it takes some time.
>>> 
>>> 
>>> 
 -Ursprüngliche Nachricht-
 Von: use-livecode  Im Auftrag 
 von matthias rebbe via use-livecode
 Gesendet: Mittwoch, 5. Mai 2021 10:31
 An: How to use LiveCode 
 Cc: matthias_livecode_150...@m-r-d.de
 Betreff: Re: notarizing DMG fails
 
 Tiemo,
 
 i think i found the solution. I tried here myself and did als get the 
 error "this identity cannot be used for signing code" when using the 
 Developer ID Installer certificate for signing the .pkg.
 According to Apple (see point 2)
 https://help.apple.com/xcode/mac/current/#/deve51ce7c3d
 
 you have to use the tool productsign to sign the package installer. 
 
 So the syntax is like this
 
 productsign --sign
 
 
 Example
 productsign --sign "Developer ID Installer: Matthias Rebbe ()"  
 "/users/matthias/LC/builts/test/test.pkg" 
 "/users/matthias/LC/builts/test/test_signed.pkg"
 
 After successful signing i got this messages in Terminal
 
 productsign: using timestamp authority for signature
 productsign: signing product with identity "Developer ID Installer: 
 Matthias Rebbe ()" from keychain 
 /Users/matthias/Library/Keychains/login.keychain-db
 productsign: adding certificate "Developer ID Certification Authority"
 productsign: adding certificate "Apple Root CA"
 productsign: Wrote signed product archive to 
 /users/matthias/LC/builts/test/test_signed.pkg

Re: Problems with Multiple Monitors

[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

which entity has to be notarized/stapled?

[Tiemo via use-livecode]

One question is left for me about notarization and stapling. If you have an 
app, which is packaged and the package is wrapped in a DMG, which instance 
should be notarized and which stapled? All three, each one after the other, 
before proceeding to the next step, or only the outer shell, in this case the 
DMG?

Is the notarization/stapeling checked by the gatekeeper only once at 
installation time or at each start of the app?
If I would only notarize and staple the outer DMG, is the notarization and 
stapling be automatically issued downwards to the content of the DMG down to 
the package and the app inside the package? Or on the other hand, would it 
interfere the process, if I would do notarization and stapling at each step?

Thanks for getting some insight in gatekeepers behaviour.

@Matthias: perhaps you want to add this information also in you doc in chapter 
7 / 7.5 to clarify this question?

Thanks
Tiemo

-Ursprüngliche Nachricht-
Von: use-livecode  Im Auftrag von 
matthias rebbe via use-livecode
Gesendet: Donnerstag, 6. Mai 2021 01:18
An: How to use LiveCode 
Cc: matthias_livecode_150...@m-r-d.de
Betreff: Re: notarizing DMG fails - solved

Thanks Phil.


@all
I've updated the lesson at

https://lessons.livecode.com/m/4071/l/1122100-codesigning-and-notarizing-your-lc-standalone-for-distribution-outside-the-mac-appstore

now and added detailed information about package installers. 
So it now contains also information about how to create,sign and notarize 
package installers or package installers on dmg.


It would be really awesome, if someone could check it. I needed to insert some 
additional steps and i really hope that i did not forget to adjust some 
references to internal steps.

So please let me if you find any errors, typos or wrong information.

Thanks.

Matthias


> Am 05.05.2021 um 19:49 schrieb Phil Davis via use-livecode 
> :
> 
> Thank you Matthias! Your tools make my life SO much easier! You have 
> done a great service for this community.
> 
> Phil Davis
> 
> 
> On 5/5/21 2:20 AM, matthias rebbe via use-livecode wrote:
>>> Am 05.05.2021 um 11:10 schrieb Tiemo via use-livecode 
>>> :
>>> 
>>> Thank you all for helping my lost soul in Apples notarizing nirvana
>>> 
>>> Tiemo
>>> 
>>> P.S.
>>> Matthias, perhaps you want to add this in your great helpfile - without 
>>> that it would have taken weeks for me!
>>> 
>> I am currently working on it. ;)
>> First i will just add a note, but later, when i have more free time  i will 
>> enhance it to describe all more detailed.
>> 
>> The Helper Stack will also get an update to support package installers. But 
>> it takes some time.
>> 
>> 
>> 
>>> -Ursprüngliche Nachricht-
>>> Von: use-livecode  Im Auftrag 
>>> von matthias rebbe via use-livecode
>>> Gesendet: Mittwoch, 5. Mai 2021 10:31
>>> An: How to use LiveCode 
>>> Cc: matthias_livecode_150...@m-r-d.de
>>> Betreff: Re: notarizing DMG fails
>>> 
>>> Tiemo,
>>> 
>>> i think i found the solution. I tried here myself and did als get the error 
>>> "this identity cannot be used for signing code" when using the Developer ID 
>>> Installer certificate for signing the .pkg.
>>> According to Apple (see point 2)
>>> https://help.apple.com/xcode/mac/current/#/deve51ce7c3d
>>> 
>>> you have to use the tool productsign to sign the package installer. 
>>> 
>>> So the syntax is like this
>>> 
>>> productsign --sign
>>> 
>>> 
>>> Example
>>> productsign --sign "Developer ID Installer: Matthias Rebbe ()"  
>>> "/users/matthias/LC/builts/test/test.pkg" 
>>> "/users/matthias/LC/builts/test/test_signed.pkg"
>>> 
>>> After successful signing i got this messages in Terminal
>>> 
>>> productsign: using timestamp authority for signature
>>> productsign: signing product with identity "Developer ID Installer: 
>>> Matthias Rebbe ()" from keychain 
>>> /Users/matthias/Library/Keychains/login.keychain-db
>>> productsign: adding certificate "Developer ID Certification Authority"
>>> productsign: adding certificate "Apple Root CA"
>>> productsign: Wrote signed product archive to 
>>> /users/matthias/LC/builts/test/test_signed.pkg
>>> 
>>> 
>>> Regards
>>> 
>>> -
>>> Matthias Rebbe
>>> Life Is Too Short For Boring Code
>> 
>> ___
>> 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
> 
> --
> Phil Davis
> 503-307-4363
> 
> 
> ___
> 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://