I am, amongst several other things we need not discuss here, an early adopter, and am currently running
macOS 11.0 beta 5 on my 2018 Mac Mini:
-
-
and notice that IDE dialogue windows do NOT respond to mouseClick: the default button only responding to
the RETURN key:
-
-
LC 9.6.1
IDE dialogue windows not working with macOS 11
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- Livecode Opensource Backer
- Posts: 9378
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
-
- Livecode Staff Member
- Posts: 818
- Joined: Fri Feb 06, 2015 4:03 pm
Re: IDE dialogue windows not working with macOS 11
Hello Richmond,
I am not able to reproduce this. Moreover, the closing dialog appears above the stack window, and the stack window is disabled.
I can click all 3 buttons, as expected. What is the exact recipe you are following?
Kind regards,
Panos
--
I am not able to reproduce this. Moreover, the closing dialog appears above the stack window, and the stack window is disabled.
I can click all 3 buttons, as expected. What is the exact recipe you are following?
Kind regards,
Panos
--
-
- Livecode Opensource Backer
- Posts: 9378
- Joined: Fri Feb 19, 2010 10:17 am
- Location: Bulgaria
Re: IDE dialogue windows not working with macOS 11
This results when I choose the menuItem:
File/Close and Remove From Memory
File/Close and Remove From Memory
-
- Livecode Staff Member
- Posts: 818
- Joined: Fri Feb 06, 2015 4:03 pm
Re: IDE dialogue windows not working with macOS 11
Hello Richmond,
Thanks for the update. I confirm what you describe. It looks like the "as sheet" is causing this behavior.
We will keep an eye - just in case this is a Big Sur beta bug that will be fixed in the next beta - otherwise this is a LC bug we need to fix.
Since you discovered it, would you mind filing a BZ report about this?
Kind regards,
Panos
--
Thanks for the update. I confirm what you describe. It looks like the "as sheet" is causing this behavior.
We will keep an eye - just in case this is a Big Sur beta bug that will be fixed in the next beta - otherwise this is a LC bug we need to fix.
Since you discovered it, would you mind filing a BZ report about this?
Kind regards,
Panos
--