crosshair limits update
Bug #1731369 reported by
Chad Parker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pcb |
Fix Released
|
Low
|
Chad Parker |
Bug Description
Presently there are several places in the code (notably not in crosshair.c) where the limits of the crosshair are changed.
It would be nice to centralize that and allow the crosshair to recompute and update its own limits.
Changed in pcb: | |
milestone: | none → pcb-4.1.0 |
Changed in pcb: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in pcb: | |
status: | Triaged → Fix Committed |
Changed in pcb: | |
status: | Fix Committed → Fix Released |
Changed in pcb: | |
milestone: | pcb-4.1.0 → pcb-4.1.1 |
status: | In Progress → Fix Committed |
Changed in pcb: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
A branch LP1731369 has been created.
In this branch a function called "crosshair_ update_ range" has been created. This function is now called anytime the range of the crosshair needs to be updated. Code that updates the limits of the crosshair has been removed from other locations.