Bug in nightly eeschema?


I have just tested eeschema of below beta version.
I have added a component, added some connections and no-cons.

I find, when placing tracks or no-cons to component pins, they won’t snap to the pins but may get placed slightly off, in which case ERC reports a missing connection.

Have I missed to set a “magnetic pin” option or is this a bug?


Version info:

Application: KiCad

Version: (5.99.0-3867-ga534f24fb6), release build

wxWidgets 3.0.5
libcurl/7.71.0 OpenSSL/1.1.1g (Schannel) zlib/1.2.11 brotli/1.0.7 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh2/1.9.0 nghttp2/1.41.0

Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW

Build Info:
Date: Oct 8 2020 11:16:26
wxWidgets: 3.0.5 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.73.0
OCE: 6.9.1
Curl: 7.71.0
ngspice: 32
Compiler: GCC 10.2.0 with C++ ABI 1014

Build settings:

I’m not up on the capabilities of the v6 pre-releases (v5.99 nightlies), but I thought "magnetic pin"s was a PCBNew feature, not an EESchema feature. A long standing limitation of EESchema is there hasn’t been any sort of object snap so the general advice is to only change grid for text and annotation placements if desired. Keep to a 0.1 or 0.05 grid for electrical placements (components, wires, no-connects, busses, etc).

Snapping has been added to 5.99. But because it’s a new feature it may have bugs. Please report it, but describe the situation accurately and ideally provide an example project snippet and a screencast.

Nice. I knew it was coming eventually but had forgotten if it stayed in the v6 roadmap or was pushed off into the v7 roadmap.