Cursor and pointer offset in Footprint Editor

Bug #1840417 reported by aqui_c
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Incomplete
Undecided
Unassigned

Bug Description

When using the Footprint editor, there is an offset between the mouse cursor and the crosshair. Moreover, the offset is non-linear, i.e. when I start the movement on the bottom-left, they both are at almost at the same place, but when moving to the top-right the offset becomes increasingly large.

It is also possible to see that the work area does not cover the entire window, but just a portion. I am attaching a screenshot of the problem.

I've managed to reproduce this error while creating a new footprint and when editing an existing one.

This basically renders the footprint editor impossible to utilize.

Application: ModEdit
Version: 5.1.4-e60b266~84~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-58-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.22
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.4.0 with C++ ABI 1011

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=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Tags: pcbnew
Revision history for this message
aqui_c (aqui-carattino) wrote :
Revision history for this message
aqui_c (aqui-carattino) wrote :

I can confirm this bug is NOT present with in version 5.0.2. Specifics below:

Application: kicad
Version: 5.0.2-bee76a0~70~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-58-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

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

Revision history for this message
Ian McInerney (imcinerney) wrote :

@aqui_c, do you have the canvas scaling enabled? See this other report: https://bugs.launchpad.net/kicad/+bug/1831318

Revision history for this message
aqui_c (aqui-carattino) wrote :

Thanks for the link! Indeed it seems related to the HiDPI display I have.

After going through the discussion and seeing there is a patch submitted, I went on to install the nightly build and I didn't see any problems with the footprint designer. With this version, problems seem solved. I guess this bug can be closed then.

Application: KiCad
Version: 6.0.0-unknown-206b406~100~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-58-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.22
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.4.0 with C++ ABI 1011

Build settings:
    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=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Revision history for this message
aqui_c (aqui-carattino) wrote :

Sorry for the noise. The bug is not solved.

If I select to use acceleration (when opening Pcbnew, the option does not pop up while using the footprint editor), then the bug comes back. In any case, it seems related to the other issue you linked!

tags: added: pcbnew
removed: editor footprint
Revision history for this message
Michael Kavanagh (michaelkavanagh) wrote :

You should be able to select Standard vs Accelerated graphics in the Preferences menubar menu.

Changed in kicad:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.