There seems to no longer be a way to warp the mouse position to a footprint’s origin - it will only warp to pads.
Previously, so long as “warp mouse to anchor of moved object” is enabled, the mouse would warp to either the coordinate origin / anchor of the footprint, or to one of its pads, whichever is closer. Behaviour discussed in depth in this thread.
But now, it will only warp to the nearest pad - it won’t warp to the footprint’s origin, even if that is much closer to where the mouse is.
I’ve tried unselecting “pads” in the “selection filter”, but then the mouse just fails to warp to anywhere at all.
Hopefully just a bug? Or have I misunderstood a feature or setting? I’ve hunted through the preferences, and done a search on Google and this forum.
EDIT: Something that could be affecting this behavior is the grid size. If I have a wildly oversized grid (1 inch), I can only drag each footprint from one location (normally whichever pad is closest to a grid point).
I’m getting the expected warp to anchor or pad behavior by clicking and dragging (and removing pads in the selection filter works as expected). If I use the drag hotkey (D), I always get warped to the anchor regardless of whether a pad is closer. This appears to be the same behavior as in v8.0.9. I can’t find an existing issue about this behavior, but I’m not confident that I’ve done a comprehensive search.
Application: KiCad PCB Editor arm64 on arm64
Version: 9.0.0, release build
Libraries:
wxWidgets 3.2.6
FreeType 2.13.3
HarfBuzz 10.2.0
FontConfig 2.15.0
libcurl/8.7.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.63.0
Platform: macOS Sequoia Version 15.3.1 (Build 24D70), 64 bit, Little endian, wxMac
OpenGL: Apple, Apple M2 Max, 2.1 Metal - 89.3
Build Info:
Date: Feb 19 2025 13:05:44
wxWidgets: 3.2.6 (wchar_t,wx containers)
Boost: 1.87.0
OCC: 7.8.1
Curl: 8.7.1
ngspice: 44.2
Compiler: Clang 16.0.0 with C++ ABI 1002
KICAD_IPC_API=ON
Thanks for that. Yes good point about dragging with the D key - that still does snap using the coordinate origin, so that’s a good workaround for now.
And grid size - no, I’m using 0.25mm, so that’s not the issue.
It’s still not working right - whether I move by hitting M or by clicking and holding down the mouse button to move the footprint that way, the mouse always snaps to a pad, even if it was right at or near the origin.
System info below. I mostly use a 4k monitor, but just tried on a 1080p one and same problem. It worked fine in Kicad 8.x and earlier versions - just getting this problem today since updating to V9.0.0
type or paste code hereApplication: KiCad PCB Editor x64 on x64
Version: 9.0.0, release build
Libraries:
wxWidgets 3.2.6
FreeType 2.13.3
HarfBuzz 10.2.0
FontConfig 2.15.0
libcurl/8.11.1-DEV Schannel zlib/1.3.1
Platform: Windows 11 (build 22631), 64-bit edition, 64 bit, Little endian, wxMSW
OpenGL: NVIDIA Corporation, NVIDIA GeForce GTX 1660/PCIe/SSE2, 4.6.0 NVIDIA 560.94
Build Info:
Date: Feb 19 2025 17:46:53
wxWidgets: 3.2.6 (wchar_t,wx containers)
Boost: 1.86.0
OCC: 7.8.1
Curl: 8.11.1-DEV
ngspice: 44
Compiler: Visual C++ 1942 without C++ ABI
KICAD_IPC_API=ON
