May not be a problem, just curious. Working on some small footprints, and set the grid to .001". It appears the cursor accuracy is not constant across the display, for example the cursor does show at center , 0, 0, moving away from center, after 3 or 4 mils, the cursor shows .0039, not 4. Error gets worse the farther the cursor is from center. The X, Y properties for the pad looks to be correct. Again, just curious, why?
Thanks,
Gary
I need to correct, the X, Y properties does show the error after pad placement, but can be corrected by entering the correct distance from center.
KiCad works with 32 bit integers in nanometers internally, so 0.001" is 25.4um = 25400nm and there should be no rounding errors on such a coarse grid as you are using.
I do remember some recent (weeks) bug report concerning rounding errors, but can’t recall further details.
Please tell us you exact KiCad version and OS detail in this sort of post.
Yes, Windows 10 Version 8.
Complete version information is the text copied from: KiCad / Help / About KiCad / [Copy Version Info. It’s a block of text with about 20 lines of text.
Ok, here it is,
Application: KiCad x64 on x64
Version: 8.0.0, release build
Libraries:
wxWidgets 3.2.4
FreeType 2.12.1
HarfBuzz 8.3.0
FontConfig 2.14.2
libcurl/8.5.0-DEV Schannel zlib/1.3
Platform: Windows 10 (build 19045), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
Date: Feb 23 2024 02:24:15
wxWidgets: 3.2.4 (wchar_t,wx containers)
Boost: 1.83.0
OCC: 7.7.1
Curl: 8.5.0-DEV
ngspice: 42
Compiler: Visual C++ 1936 without C++ ABI
Build settings: