new MSPointer(game) The MSPointer class handles Microsoft touch interactions with the game and the resulting Pointer objects. It will work only in Internet Explorer 10+ and Windows Store or Windows Phone 8 apps using JavaScript.http://msdn.microsoft.com/en-us/library/ie/hh673557(v=vs.85).aspx You should not normally access this class directly, but instead use a Phaser.Pointer object whichnormalises all game input for you including accurate button handling. Please note that at the current time

game : Phaser.Game A reference to the currently running game. Source code: input/MSPointer.js (Line 28)

event :MSPointerEvent | null The browser MSPointer DOM event. Will be null if no event has ever been received.Access this property only inside a Pointer event handler and do not keep references to it. Type MSPointerEvent | null Source code: input/MSPointer.js (Line 75)

enabled : boolean MSPointer input will only be processed if enabled. Default Value true Source code: input/MSPointer.js (Line 82)

capture : boolean If true the Pointer events will have event.preventDefault applied to them, if false they will propagate fully. Source code: input/MSPointer.js (Line 59)

callbackContext : Object The context under which callbacks are called (defaults to game). Source code: input/MSPointer.js (Line 39)

button : number This property was removed in Phaser 2.4 and should no longer be used.Instead please see the Pointer button properties such as Pointer.leftButton, Pointer.rightButton and so on.Or Pointer.button holds the DOM event button value if you require that. Source code: input/MSPointer.js (Line 67)

[static] WHEEL_UP : number Source code: input/Mouse.js (Line 202)

[static] WHEEL_DOWN : number Source code: input/Mouse.js (Line 208)

[static] RIGHT_BUTTON : number Source code: input/Mouse.js (Line 184)