locked object can be selected by the DRC operation
Bug #1394630 reported by
madGambol
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pcb |
Fix Released
|
Medium
|
Chad Parker |
Bug Description
For some objects, a DRC operation will select locked objects.
"Unselect All" won't deselect them.
Selecting another object and moving it will move locked objects selected by the DRC operation.
tags: | added: drc |
Changed in geda-project: | |
importance: | Undecided → Medium |
Changed in pcb: | |
milestone: | none → pcb-4.2.0 |
Changed in pcb: | |
importance: | Undecided → Medium |
Changed in pcb: | |
status: | New → Confirmed |
Changed in pcb: | |
assignee: | nobody → Chad Parker (parker-charles) |
Changed in pcb: | |
status: | Confirmed → In Progress |
Changed in pcb: | |
status: | In Progress → Fix Committed |
Changed in pcb: | |
status: | Fix Committed → Fix Released |
Changed in geda-project: | |
status: | New → Fix Released |
To post a comment you must log in.
I recently fixed a bug that would leave silk lines selected after a DRC. The DRC now leaves all flags in the state they were prior to executing. In the gtkhid at least, where the DRC finds all errors, then reports them as a list.
In the lesstif hid, it works one at a time. So, it's possible that if a locked object was part of a violation, it will be selected. If the user cancels the DRC, it will leave the object selected, however, it does not allow the locked object to be moved.
It is still the case that "unselect all" does not unselect the selected locked object. So, part of this bug is still valid.