pcb

Crosshair Initialization

Bug #1731375 reported by Chad Parker on 2017-11-10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	pcb	Fix Released	Low	Unassigned	pcb pcb-4.1.1

Since the crosshair is also used by the batch HID, its initialization should not be restricted to gui HIDs.

Revision history for this message

Chad Parker (parker-charles) wrote on 2017-11-10:

Branch LP1731375 fixes this.

Eventually, I think that the crosshair should be initialized only by the HIDs that use it, but we're not there yet.

Bert Timmerman (bert-timmerman) on 2017-11-12

Changed in pcb:
milestone:	none → pcb-4.1.0

Bert Timmerman (bert-timmerman) on 2017-11-23

Bert Timmerman (bert-timmerman) on 2017-11-25

Changed in pcb:
status:	Triaged → Fix Committed

Bert Timmerman (bert-timmerman) on 2018-01-21

Revision history for this message

Chad Parker (parker-charles) wrote on 2018-01-27:

I see you reverted this... was it causing a problem?

Revision history for this message

Bert Timmerman (bert-timmerman) wrote on 2018-01-27:

Yup,

Needed to get the above out of the way soonish as it was/is spoiling a release.

Just get our thinking hats on again ;-)

Kind regards,

Bert Timmerman.

Revision history for this message

Chad Parker (parker-charles) wrote on 2018-02-25:

The error fixed by reverting this and LP1731369 are fixed by LP1744589. I think all three can go in.

Bert Timmerman (bert-timmerman) on 2018-02-25

Changed in pcb:
status:	In Progress → Fix Committed

Bert Timmerman (bert-timmerman) on 2018-04-07

Changed in pcb:
status:	Fix Committed → Fix Released

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.