Do not simulate a mouse event on primary touch point events

[jgranick]

Instead of simulating mouse events on primary touch events, Lime should dispatch these events separately, and allow developers to handle both cases distinctly.

If we wish to have a unified mouse/touch event interface, we could consider a pointer event, to help make this more clear

[player-03]

Problem is, lots of devs will have programmed their buttons to respond only to mouse events. After all, mouse events work consistently across devices.

Pointer events sound fine, but I still don't see the benefit. Why do these cases need to be handled distinctly? Is it really that important to distinguish between a mouse and a touchscreen? It's incredibly rare for both devices to be in use at once. (And if it's that important, the programmer can still tell the difference: one device dispatches two events, the other dispatches one.)