Event bubbling

[hyperandroid]

Test the convenience of a consumed parameter to input events which will set the event as consumed or not. If the event is not consumed, the input subsystem will continue traversing the scene graph finding suitable actors to consume the event. Implications:

• create a method findAllActorsAtPos which will traverse the whole scene graph and return an Array of Actor elements which lie at any given on-screen coordinate.

[robboerman]

Does this have to do with the following too?

I want to create an ActorContainer that can be dragged and that contains Actor children. The Actor children should respond to clicks. At the moment this is not possible. If the Actor has enabled events, all events stop at the actor and the Actor Container's mouseClick and mouseDrag callbacks are never called. Another example is when a Actor Container contains Actors that have events disabled. The events again stop at the actor because the Actor has mouseEnabled set to false.

[hyperandroid]

Yes. With the possibility of programmatically let the input traversal function to find other suitable actors to receive the input event. Will make some tests to realize whether it is suitable to be added to caat or not.

[robboerman]

What is also possible is a manual bubble to parents. At the moment Actors contain all mouse handler stubs. That stub could also do a call on the object's parent (mouseDown: function(eventObject) {if (this.parent.mouseEnabled) this.parent.mouseDown.call(eventObject);} That way you would not have to change anything in the findActor part but just let actors that are found pass the event along

(don't know exactly if this works with the mouse coordinates though)

[blake8086]

This would be great, I'm having an issue with this right now (I want to be able to drag the mouse with the button held down over multiple Actors and have them all notice).

[hyperandroid]

CAAT 0.3 build 208.

• Added to CAAT.Scene the following methods:
  • findActorAtPosition(CAAT.Point) : custom actor find procedure. This is overriden to attend at the priority input lists.
  • enableInputList(number) : number of priority lists to set for this scene. A priority list is a list of actors to which are suitable to receive input first. If no actor on the priority lists are under the cursor, the whole scene graph is traversed instead.
  • addActorToInputList( actor, index, position ) : add an actor to a given priority list at certain position.
  • emptyInputList( index ) : remove all elements from a list.
  • removeActorFromInputList( actor, index ) : remove an actor from a list, or if no index list is supplied remove the actor from every list in which appears.