grab of directly connected symbols causes loss of connection

Bug #1798968 reported by Thomas Pointhuber
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KiCad
Fix Committed
Wishlist
Jeff Young

Bug Description

# HowTo Reproduce

1. place two resistors, one pin directly overlaps with the second one (and is marked connected)
2. grab resistor and move

you expect that the resistor is still connected after the move, but the connection is lost. This is because no track was present in the initial state, and the grab would need to add a new track to keep the connection alive.

https://cloud.oe5tpo.com/s/9BtjZR9AmiySeYs

# System Information

Application: kicad
Version: (6.0.0-rc1-dev-942-g38c5b025c), debug build
Libraries:
    wxWidgets 3.1.1
    libcurl/7.61.1 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.34.0
Platform: Linux 4.18.14-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.1.1 (wchar_t,wx containers) GTK+ 2.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: Clang 7.0.0 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Seth Hillbrand (sethh)
Changed in kicad:
importance: Undecided → Low
status: New → Triaged
milestone: none → 5.1.0
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 353bda6792c5af26b98adf3ab3d040fc476c3777
https://git.launchpad.net/kicad/patch/?id=353bda6792c5af26b98adf3ab3d040fc476c3777

Changed in kicad:
status: Triaged → Fix Committed
assignee: nobody → Seth Hillbrand (sethh)
Revision history for this message
Thomas Pointhuber (pointhi) wrote :

@sethh, this fix does not seem to work correctly.

When I Grab a symbol now which is directly connected with another symbol, the other symbol is moved as well with it (like if those two symbols are in fact a single one).

The expected behavior would be that the second symbol stays where it is, and there are wires added to the moved one connecting to the second symbol.

Changed in kicad:
status: Fix Committed → Confirmed
Revision history for this message
Seth Hillbrand (sethh) wrote :

That's one way of looking at it. But we don't support rubberbanding at the moment (lp: 594054), so the new requirement will need to wait for that to be implemented.

Changed in kicad:
assignee: Seth Hillbrand (sethh) → nobody
importance: Low → Wishlist
milestone: 5.1.0 → 6.0.0-rc1
Revision history for this message
Thomas Pointhuber (pointhi) wrote :

I don't think thats rubberbanding what the bug report is about. It's more about simply keeping the connection (adding wires if required)

Revision history for this message
Seth Hillbrand (sethh) wrote :

We could add a new wire to the schematic that doesn't respect user preferences but I'd prefer not to do that. And this edges into new feature territory. This is something that we can address in the new toolset during v6, not for 5.1

Revision history for this message
Thomas Pointhuber (pointhi) wrote :

the new behaviour of eemodern is similar to the old one, but it looses connection of indirectly connected nets.

With the new toolset this issue can be properly fixed

tags: added: eemodern
Jeff Young (jeyjey)
Changed in kicad:
assignee: nobody → Jeff Young (jeyjey)
status: Confirmed → In Progress
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

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

Changed in kicad:
status: In Progress → Fix Committed
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.