Events from PSwing components are not consumed, and cause other interactions on the canvas

[GoogleCodeExporter]

Events from PSwing components are not consumed, and cause other interactions on the canvas

[GoogleCodeExporter]

Original comment by steveonjava on 25 Jun 2008 at 6:35

• Added labels: Milestone-1.3

[GoogleCodeExporter]

Original comment by steveonjava on 2 Jul 2008 at 12:28

• Added labels: Milestone-2.0

[GoogleCodeExporter]

Original comment by steveonjava on 3 Jul 2008 at 5:05

• Added labels: Milestone-1.3

[GoogleCodeExporter]

Committed to trunk.

commit -m "Issue 15 ; properly consume mouse events in PSwing components"
    Sending       
piccolo2d.java-trunk/core/src/main/java/edu/umd/cs/piccolo/util/PPickPath.java
    Sending       
piccolo2d.java-trunk/extras/src/main/java/edu/umd/cs/piccolox/pswing/PSwingEvent
Handler.java
    Transmitting file data ...
    Committed revision 393.

Original comment by [email protected] on 7 Oct 2008 at 8:23

• Changed state: Fixed

[GoogleCodeExporter]

I think this causes problems with the zoom handler. If you start zooming 
outside a
swing component and then release the right mouse button over one, zooming is 
still
active, even though the right mouse button has been released. 

Original comment by allain.lalonde on 23 Oct 2009 at 9:06

[GoogleCodeExporter]

Although, strictly speaking this issue is fixed since PSwing now consumes 
events that
take place over it, it doesn't play nice with the other event handlers.

For example, mouse up using the Zoom Handler. The PSwing examples are terrible 
if you
try to zoom zoom and happen to end it over a PSwing node.

How should this be dealt with?

Original comment by allain.lalonde on 5 Nov 2009 at 4:46

[GoogleCodeExporter]

Marking this issue as Verified; created a new Issue 154 for the problem 
described in
comments 5 and 6 above.

Original comment by [email protected] on 18 Dec 2009 at 5:39

• Changed state: Verified