Key press events create new event objects for each node

[orange451]

Key press events create new event objects for each node

[orange451]

Question to you, if the event is consumed, should it still be passed to the child node?

[Peanhua]

The behavior should be that passing the event is stopped when someone consumes it.

The isConsumed() check can be done in the application code, but this check would need to be present on every event handler.

Also JavaFX stops passing the event when it is consumed, see the "capturing phase" in https://docs.oracle.com/javafx/2/events/processing.htm
The "bubbling phase" would be nice to have too :)

[orange451]

I pushed a change. It isn't exactly what you want, but it should help. Key events now all share the same event object, additionally the event is fired from the lowest descendant node and moves upwards towards the scene.

[orange451]

In the future I'll see if we can work to a more JavaFX styled event system.

[Peanhua]

Thanks :) It does help, sharing the same object is the most important thing, anything else can be worked around in the application code.

[Peanhua]

I am not sure if you wanted to keep this open or not, but from my point of view it can be closed.