Bug in recent nightly Moving Fab Layer Text Breaks Fill Net Connection

At the moment, very repeatable:


This is from the 10JUN18 nightly “kicad-r10501.72b49accc-x86_64.exe”

Application: kicad
Version: (5.0.0-rc2-154-gb82bf7c44), release build
Libraries:
wxWidgets 3.0.3
libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.60.0
OpenCASCADE Community Edition: 6.8.0
Curl: 7.54.1
Compiler: GCC 7.1.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=ON
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=ON

Clicking “b” or “F9 then F11” gets it back to normal.
This may already have been fixed with a newer nightly.

Secondly, I have been using this nightly without issue, until I did a complete wipe of KiCad off of my machine, regedit out every kicad instance and removing every instance of kicad (and settings files) in user folders.
Essentially, it should have been a “clean” installation.

Anyone else have this issue?

Hmm, not sure that’s ‘breaks fill net connection’, as the net name is still correctly applied.
What it looks to be doing, is taking a shift in any part entity XY, as a seed to refresh the non pour ratsnests.
ie assumes fill may no longer be valid for that part.

  • looks like any edit of the part (eg even a flag from visible to invisible) does the same thing.
    Not sure that’s too big a problem ?

Might confuse users.

Probably this one:

3 Likes

Looks to have been fixed in the last few days. Perhaps the OP can check ?

I’m out of data until 4 or 5 days.
@Seth_h I’m not well versed at finding bugs at the bug tracker. Thanks for finding it and confirming that it is a known bug.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.