On 6/28/2019 8:04 PM, doc hawk via use-livecode wrote:
On Jun 28, 2019, at 8:24 AM, Paul Dupuis via use-livecode
<[email protected]> wrote:
When the standalone opens the external stack (which could be in an older stack
file format), when the mouse is in the external stack window, LiveCode thinks
the mouse is about 30-40 pixels ABOVE where the mouse actual is.
I may be seeing something related to this in the IDE, I think, under High
Sierra. It didn’t do it in 9.0.
I see it manifest most often when the application browser is on the secondary
screen. And then *mumble* happens, and when I select a control on the from the
list to open an inspector, I get an inspector for the wrong object.
Hmm, on further thought, maybe not: it seems to select the correct item on
screen, and inquiries about the selectedObject yield the correct object.
If I move the application browser back to the main screen, release, and drag.
Back, sometimes (but not always) it fixes this
Thank you for possible conforming, but this is not seen in the IDE. Jut
in the built Standalone. It is also very clear that LiveCode thinks the
mouse is 20-40 pixels towards the top of the window than it actually is.
If I want to click on a button, I don't put the mouse over the button
but about 30px under the bottom and click and the button hilites and
functions.
I think Richard Gaskin has the best educated guess on this. It's like
LiveCode is compensating for a Mac Menubar for that stack that isn't there.
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode