Issue 15 in piccolo2d: Events from PSwing components are not consumed, and cause other interactions on the canvas

[codesite...@google.com]

Issue 15: Events from PSwing components are not consumed, and cause other
interactions on the canvas
http://code.google.com/p/piccolo2d/issues/detail?id=15

Comment #4 by heuermh:
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/PSwingEventHandler.java
Transmitting file data ...
Committed revision 393.

Issue attribute updates:
Status: Fixed

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #5 on issue 15 by allain.lalonde: Events from PSwing components are

not consumed, and cause other interactions on the canvas
http://code.google.com/p/piccolo2d/issues/detail?id=15

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.

[picc...@googlecode.com]

Comment #6 on issue 15 by allain.lalonde: Events from PSwing components are

not consumed, and cause other interactions on the canvas
http://code.google.com/p/piccolo2d/issues/detail?id=15

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?

[picc...@googlecode.com]

Updates:
Status: Verified

Comment #7 on issue 15 by heue...@gmail.com: Events from PSwing components

are not consumed, and cause other interactions on the canvas
http://code.google.com/p/piccolo2d/issues/detail?id=15

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