We are currently doing some work to improve blueprint's SyntheticEvent implementation. MouseEvent is gaining adoption of properties like target, relatedTarget, shitKey etc. It could be very useful to provide a TouchEvent for some applications.
This should match the spec here as close as possible: https://developer.mozilla.org/en-US/docs/Web/API/TouchEvent
Ideally we would provide the following set of events: onTouchCancel onTouchEnd onTouchMove onTouchStart. See: https://reactjs.org/docs/events.html
As per this forum post JUCE has a MultiTouch example we could leverage:
https://forum.juce.com/t/how-to-do-ios-style-multitouch-handling/23936
It may be that we need to provide some mechanism to opt into this behaviour as the C++ side of generating TouchEvents is sure to incur some level of overhead.
We are currently doing some work to improve blueprint's
SyntheticEventimplementation.MouseEventis gaining adoption of properties liketarget,relatedTarget,shitKeyetc. It could be very useful to provide aTouchEventfor some applications.This should match the spec here as close as possible: https://developer.mozilla.org/en-US/docs/Web/API/TouchEvent
Ideally we would provide the following set of events:
onTouchCancel onTouchEnd onTouchMove onTouchStart. See: https://reactjs.org/docs/events.htmlAs per this forum post JUCE has a MultiTouch example we could leverage:
https://forum.juce.com/t/how-to-do-ios-style-multitouch-handling/23936
It may be that we need to provide some mechanism to opt into this behaviour as the C++ side of generating TouchEvents is sure to incur some level of overhead.