> On Jun 22, 2026, at 9:35 PM, Patrick Luby <[email protected]> wrote:
>
>
>
>> On Jun 22, 2026, at 1:31 PM, Dan Williams <[email protected]> wrote:
>>
>> Yeah, ton of work still; slowly getting spacing/margins/etc where I think
>> they should be. It’s an interesting exercise and welded dialogs actually
>> look pretty good on macOS.
>
> I’m sure we’ll have to reimplement a bunch of little macOS bug fixes that are
> in the vcl/quartz and vcl/osx code. The fix for live resizing that forces a
> bunch of LibreOffice timers to run immediately still makes me wince every
> time I open vcl/osx/salframeview.mm. :/
I do wonder how much Qt handles internally on Mac though; perhaps they’ve fixed
some of those issues already.
>
>> High DPI is still WIP; when I make it look OK with Qt it isn’t right with
>> the Aqua plugin. Haven’t debugged that yet, focusing on the spacing stuff.
>
> Any chance you could put some #ifdef SOME_NEW_MACRO around your HiDPI code
> and commit it to your private branch? I have some time this week to debug.
> Might also give me an entry point for understanding the Qt6 vcl
> implementation.
I’d love to either figure out a non-ifdef solution or to push it down to the
VCL plugin. I have two patches in the private branch:
vcl/qt: use physical DPI rather than logical to handle HighDPI
vcl/window: use 72 DPI for Mac
That if applied make the qt6 Mac VCL plugin look OK, but make Aqua/non-Mac-Qt
look bad. One works for text and the other to graphics (not surprised, but I
didn’t expect to have two different paths like this). Some of it is cribbed
from the existing Aqua plugin.
Those patches cleanly revert so you can test/debug fairly easily that way if
you like.
Dan
