pcbnew GAL: reset local coordinates not snapped to grid

Bug #1671869 reported by Eldar Khayrullin
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Undecided
Unassigned

Bug Description

See the attachment.
dx, dy, dist have non-zero values after press btn 'Space' if draw or place something.

Application: kicad
Version: no-vcs-found-0be5645~58~ubuntu16.10.1, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.50.1 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.33 librtmp/2.3
Platform: Linux 4.8.0-41-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.61.0
Curl: 7.50.1
KiCad - Compiler: GCC 6.2.0 with C++ ABI 1010
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  KICAD_SCRIPTING_ACTION_MENU=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON

Tags: gal pcbnew
Revision history for this message
Eldar Khayrullin (eldar) wrote :
Revision history for this message
John Beard (john-j-beard) wrote :

Space does actually work, but when drawing, it takes the exact mouse pointer position, not the snapped-to-grid cursor (the white cross) position. This makes it basically impossible to get an accurate reading for drawing actions on the grid (unless you can do the rounding in your head, and your mouse pointer was close enough to the cursor at the time!).

summary: - pcbnew: non-zero reset local coordinates if draw or place something
+ pcbnew GAL: reset local coordinates not snapped to grid
Changed in kicad:
status: New → Confirmed
Revision history for this message
Andrey Kuznetsov (kandrey89) wrote :

There needs to be 2 modes in which dx/dy work:
1. snap to grid
2. freehand

The reason for freehand is because if you're not on a grid, like rounded corners, and you need to make sure the narrowest point is at least X, you use the mouse to check, and it won't be precise enough if it's snapping to large grid points instead.

I've found that while editing footprints in Cairo, software would start behaving oddly, stop snapping to grid, or stop performing freehand, and also stop updating dx/dy values no matter where the mouse is moved although spacebar would update the dx/dy but no updates on mouse movement. I've also had bugs where select/delete would not work on a simple line, and I had to restart Footprint editor for the aforementioned problems to go away.

Changed in kicad:
milestone: none → 5.0.0-rc1
Revision history for this message
Oliver (schrodingersgat) wrote :

I can also confirm this bug - it appears that when you press Space to "reset" the local origin, it takes the origin point for delta-measurement (dx/dy) not from the closest grid point but from the exact mouse pos (as John notes, above).

This *used to work as intended* however at some recent stage the behaviour has changed. Any chance this could be addressed (just this measurement bug, not the "dual modes" as suggest above) soon, rather than waiting for 5.0.0?

Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 481fd233d49f640ed38ee252b7810cc25a58c96c
https://git.launchpad.net/kicad/patch/?id=481fd233d49f640ed38ee252b7810cc25a58c96c

Changed in kicad:
status: Confirmed → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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