wxWidgets gets wrong rendering area on scaled high DPI monitors

[evils]

Please fill out the following:

• Sway Version: 1.8.1

• Debug Log:

  • omitted due to failure to reproduce the intermittent issue, interruption to my desktop usage and a previous failed attempt to collect a log

• Configuration File:

  • I believe it should reproduce on a default config with additional config like this (from my config verbatim)

    output "Samsung Electric Company LU28R55 HNMW104971"    position 1200 188 res 3840x2160
    output "Samsung Electric Company LU28R55 HNMW104971"    scale 1.398438
    output "Samsung Electric Company LU28R55 HNMW104969"    position 3945 188 res 3840x2160
    output "Samsung Electric Company LU28R55 HNMW104969"    scale 1.398438
    output "Eizo Nanao Corporation EV2436W 65118044"        transform 90
    output "Eizo Nanao Corporation EV2436W 65118044"        position 0 0

• Stack Trace:

  • no crashing involved

• Description:

  • KiCad (and wxWidgets) recently started to get Wayland support working, in testing these changes i found an issue which i assume the KiCad contributor could not reproduce on Gnome, because they suggested i open an issue here
  • screenshot copied from that issue showing the main KiCad window in the background, and a floating sub-program window on top, showing the rendered area exceeding the window decoration
  • i believe the issue is that on a scaled DPI monitor, KiCad receives the wrong area to render into (or the wrong window size?)
  • the wxWidgets cube sample exhibits the same issue
  • while i've been able to trigger apparently semi-persistent correct behaviour by unplugging and replugging some monitors, it also seems to spontaneously go away and i'm unable to making capturing debug information problematic
  • this is on KiCad master on wxWidgets 3.2.3 on Sway 1.8.1 on NixOS unstable

[evils]

currently i'm getting the inverse symptom on my scaled 4k monitors cube works as expected, but on my unscaled 1200p monitor i get this

[bl4ckb0ne]

Can you provide a client log using WAYLAND_DEBUG=1 please?

[evils]

after waking my desktop after a suspend i'm back to KiCad not working right on the scaled monitors and Cube working right on unscaled

now neither work right on the scaled monitors and only work right on the unscaled monitor after toggling between fullscreen and floating (forcing the full render area into the unscaled monitor?)

attached is a video of my unscaled monitor and the full text output of the debug enabled Cube shown

https://github.com/swaywm/sway/assets/30512529/192dfb79-6a32-45b5-be5a-625f3ea5cb4f

wxGTK-Cube_sway.log

[kuon]

For reference: https://gitlab.com/kicad/code/kicad/-/issues/18079