0000514: Code Responds To Wrong Button Events

(0001154)
sean94z (reporter)
2012-01-26 16:39

Right, IIRC some buttons behave as they should. Must have been those first couple buttons that were added that slipped though the cracks.

(0002691)
sean94z (reporter)
2013-07-07 06:53

Mike, can you advice as to which signal would be the best solve this problem?

(0002739)
malcom2073 (updater)
2013-11-27 21:10

clicked() is proper, not mousePressed. This handles the case where you click down, move off and release, and does not trigger in that situation.

(0002740)
sean94z (reporter)
2013-11-27 22:08

commit 7637a6f4fe775f60c55c3cd2d2202bcc2739952e
Author: Sean Keys <skeys@athenawave.com>
Date: Wed Nov 27 15:10:13 2013 -0700

[514] Fixed as per Mikes suggestion. I'm going to assume
that's as good as it gets within reason.

Notes
(0001154) sean94z (reporter) 2012-01-26 16:39	Right, IIRC some buttons behave as they should. Must have been those first couple buttons that were added that slipped though the cracks.

(0002691) sean94z (reporter) 2013-07-07 06:53	Mike, can you advice as to which signal would be the best solve this problem?

(0002739) malcom2073 (updater) 2013-11-27 21:10	clicked() is proper, not mousePressed. This handles the case where you click down, move off and release, and does not trigger in that situation.

(0002740) sean94z (reporter) 2013-11-27 22:08	commit 7637a6f4fe775f60c55c3cd2d2202bcc2739952e Author: Sean Keys <skeys@athenawave.com> Date: Wed Nov 27 15:10:13 2013 -0700 [514] Fixed as per Mikes suggestion. I'm going to assume that's as good as it gets within reason.

Relationships