On 2024-02-10 21:16, Paul Dupuis via use-livecode wrote:
My desktopChanged handler, at one point, executes either a:
set the effective width of window tWindow to tMontiorWidth
OR a
set the effective height of window tWindow to tMonitorHeight
Either of which sends a resizeStack message to th
Paul:
> So, I finally tracked this maximization weirdness down.
Good job cracking the case, for this particular maximization example!
> The issue also only occurs if the resizeStack handler
> for the window uses the passed parameters
BEST PRACTICE for LC:
1. Instead of param, use property suc
So, I finally tracked this maximization weirdness down.
This only occurs on macOS when a window is maximized using the titlebar
maximization icon (which cause teh window to go to fullscreen, hiding
the window titlebar and macOS menubar. The menubar and titlebar
re-appear if your roll the mouse
It may be that. I have to figure out a work-around. I will keep
properties in mind as I dig into the resizeStack handlers.
And yet, I shouldn't have to figure out a work-around. Since it works on
Sonoma and Windows 11, it really SHOULD work on Mojave (and Monterey and
all supported versions of
What I find most curious is that the Autocode window does show a few controls
that look to be placed correctly at the bottom of the window. My guess is that
it is a timing issue and you are using a property value that isn’t yet updated.
That is probably (hopefully) going to be a good place to
So , for any one interested, here are screenshots of what is happening.
The "Autocode" window (stack) and the "Search Sources" window (stack)
are two example of the windows that do NOT maximize correctly. Many
other resizable windows do so just fine and windows with both fewer and
more controls
Paul:
> on certain macOS versions, maximizing the window results in
> no controls being drawn or most controls being drawn incorrectly.
When drawn incorrectly, are controls the wrong sizes/rects?
Or content/visual glitches? Of what nature?
Thought it might be worth following up, in case anyon
I've seen maximization issues, and been blamed for LC/OS tendencies!
1. Can you make a bare bones test stack to trigger the issue?
That would lead to bug report or a code fix/workaround.
2. Separately: LC needs maximizeStack msg and maximized window property.
Good use cases, plus another wor
