Viewport is quarter size on HiDPI Screens in 5.1.4

[Michael Platzer]

Application: KiCad
Version: 5.1.4, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh2/1.8.2 nghttp2/1.39.2
Platform: Linux 5.2.7-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.69.0
    OpenCASCADE Technology: 7.3.0
    Curl: 7.65.3
    Compiler: GCC 9.1.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=ON
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=OFF
    KICAD_USE_OCC=ON
    KICAD_SPICE=ON

Steps to reproduce:
1. Open Eeschema or Pcbnew (either from a project or the standalone version)
2. Make sure that under "Preferences" the "Modern Toolset (Accelerated)" is selected

I use Gnome 3.32.2 as Desktop and since I have a HiDPI screen, I am using the 200 % scaling option.

Note: mouse events seem to be registered with the correct scaling

[Jamie McClymont (jamie-mcclymont)]

I can reproduce this against a similar build in GNOME but not KDE (where it scales as expected).

I see that KDE sets GDK_SCALE=2 and GDK_DPI_SCALE=0.5 on the process, where GNOME provides no scaling-related environment variables.

[Ian McInerney (imcinerney)]

Have you tried modifying the canvas scale option in the preferences' dialog to match the system scaling?

[Michael Platzer (michael.platzer)]

Thanks, that works. Setting the canvas scale to 2 fixes the viewport scaling.

The scaling is also fine when I set the environment variables as suggested by Jamie (and set the canvas scaling to automatic mode).

[Ian McInerney (imcinerney)]

This is technically a duplicate of bug lp:1797308, but I am going to leave this one separate and mark it as won't fix since it provides a nice concise documentation of the resolution of the issue (the other report dives more into the internal technical details). It is going to be won't fix since it is technically a wxWidgets problem, and we have already provided a workaround.

These issues will also be documented on the website on the known system issues page soon (https://github.com/KiCad/kicad-website/pull/443).