https://bugs.documentfoundation.org/show_bug.cgi?id=141578
--- Comment #50 from Michael Weghorn <[email protected]> --- (In reply to Michael Weghorn from comment #48) > > 5. I may be wrong, but I am getting the impression that either: the issue is > > not easily fixable (...) > > From how I understand it (reading Jan-Marek's earlier comments), it's indeed > not easily fixable and requires not only work on the Qt VCL plugin, but also > down deep in the central rendering code, which makes it time-consuming and > also potentially risky to break other things and thus needs extra care. Of > course, it might be possible that there's an easier approach that nobody > came up with yet... One aspect to mention here: There's currently an Outreachy project to implement Qt welding (see bug 130857), i.e. using native Qt widgets and letting Qt handle the rendering. For those widgets that are converted to this approach, I'd expect that the use case described here should "just work" in general. I've just tried one of the simple message dialogs that were converted to the new approach in commit 1ace888823443b85d4a81b94656844f1b27e2987 Author: OmkarAcharekar Date: Wed Dec 20 19:13:50 2023 +0530 tdf#130857 Use native qt widgets - simple message dialog and that indeed works fine when moving the dialog between the 2 screens using different scale factors. Whether implementing all of the existing weld API for Qt will by itself be sufficient is something I'm unsure of yet, though. (But if gtk3 works fine, that might be related to it using native Gtk widgets already for most of the UI.) -- You are receiving this mail because: You are the assignee for the bug.
