PNS Router marks previous segments of track as collisions
Bug #1762043 reported by
Jeff Young
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| KiCad |
Fix Released
|
Medium
|
Jeff Young | ||
Bug Description
Running the PNS router in Highlight Collisions mode works fine for the first unconnected track.
However, the next time you route an unconnected track, m_currentNet will have been decremented to -1. As you route, though, any fixed segments still get set to 0, which causes them to be highlighted as collisions (because -1 != 0).
@Tom, why do we decrement unknowNetIdx each time we create a new unconnected track? Is there a reason it can't just be left at 0?
Revision history for this message
| Jeff Young (jeyjey) wrote | #1 |
| tags: | added: pns |
| description: | updated |
Revision history for this message
| KiCad Janitor (kicad-janitor) wrote | #2 |
| Changed in kicad: | |
| status: | New → Fix Committed |
| assignee: | nobody → Jeff Young (jeyjey) |
| Changed in kicad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note that the fact that a collision exists means you can't connect the track to anything (or fix any other points) unless you're in "Allow DRC violations" mode.