The events component in Phaser ce adds event handers to a display object such as onInputDown, and onDragStop. They just need to enable them with certain booleans, and I am ready to go with handing input for a certain display objects in a project. This post will be a general overview of how to get going with the events for the display object component.
In this post I was using phaser 2.11.0 when ruining the examples.
Just about all events in phaser ce are instances of Phaser.Signal, this is a class in phaser that allows for attaching more than one event handler and can also be used to create your own events as well.
In order to get started with drag events in addition to setting the inputEnabled bool to true, there is also an additional bool to set true in the inputHandler of the display object at gra.input.draggable.
You might want to check out my post on draggable input in phaser, to know a bit more about what there is to know with the inputHander.
The events object is there to play with no matter what, but I will want to set inputEnabled true or else some of the input events will not work. This also sets up an instance of inputHandler for the display object. For more on the input handler be sure to check out the post I wrote on inputEnabled component.
A context menu may show up when I long press, or right click a projects canvas element, there is of course the preventDefault method that I can call to prevent this. A reference to the canvas element can be found at game.canvas where something like this can be done:
Although The events component is there to work with off the bat there are some boolean values that need to be set true in order for any of them to work. So a basic example will involve at least a single display object that has both the events, and input components (Sprites, Graphics). This display object will have it’s input handler enabled by setting the inputEnabled boolean true, at which point a few event handlers will now work such as onInputDown.
I use the add method for a certain event handler such as onInputDown to add a single event handler to an array of methods that are to be called for that handler. That is because onInputDown is an instance of Phasers Signal Constructor, and as such works similarly to addEventListener in vanilla js, in the sense that I can have more than one callback for a certain event.
In this section I will go over some of the events in the events component, and give a basic example. I will also provide links to other relevant posts on the different events.
This is a handler that will fire when a mouse click, or touch start event occurs on the sprite, graphics or other display object. This event fires just once, and will not fire over, and over again after a pause like some other handlers.
The method that I give to the add method of the event handler will receive a reference to the relevant display object (in this post I am using Graphics rather than sprites), and a reference to a pointer object.
Same as onInputDown, but if fires when the mouse button is release, or a touch event has ended.
These are additional handlers in the events object that are fired when a mouse cursor is hovering over the display object, and when it leaves, which is useful for desktop projects.
Any drag event will involve a mouse click down, movement of the mouse, and then release of the mouse button, or a similar situation involving a touch screen. Reslulting in dragStart, dragUpdate, and dragEnd events.
It is important to Keep in mind that the dragUpdate handler seems to fire before the dragStart handler, so if I use dragStart to set something up, it might not be there the first time dragUpdate fires.
The onDestroy event fires whenever a sprite is completely removed from the cache when the destroy method is called. I have a post on the onDestroy event that gives an example of this in action.
The onKilled event differs from the onDestroy event in that this event fires when a sprite is killed, but still remains in the cache. Check out my full post on the onKilled event to read more on this one.
The events component is very useful for quickly getting started with input involving display objects. As time goes on I may update this post to reference other posts on phaser display object components as time goes by.