1. Using the touch screen, I am getting continuous callbacks, up to 8 per bloc, where the touch point has not moved at all, up to the maximum precision of "float". These can be filtered out, but it is not very efficient.
2. The Usine multitouch parameters provide an event each for X, Y and mouseDown (0=up, 1=down). This means you can always track a touchpoint, and it always has the same index in the event arrays. The sdk mouseUp and mouseDown callbacks do not provide a mouseUp / mouseDown event array, only X and Y. That means that you know one of the touch points has had Down or Up, but you cannot tell which one !
3. If I touch two points at once, I never get two X/Y events in the mouseDown callback, always one Down, and then the second point shows on the Move callback.
NOTE:
The Usine multitouch module parameters work fine, and wiring a module's X/Y/mouseDown output parameters back into some inputs to detect multitouch works fine (although a bloc delay probably occurs). But some way to go with the sdk I think ;-(
Simon.
Statistics: Posted by sm_jamieson — 20 Jan 2016, 01:38
]]>
]]>
Statistics: Posted by sm_jamieson — 18 Jan 2016, 15:41
]]>
fixed
- corrected all onMouseXXXMulti callbacks in UserModule
improvements
- sdkGetUsineVersionType() and TUsineVersionType enum to get the flavor of the usine distrib
- added a int universeNum parameter to onDMXSendOut callback for DMX device who can deal with more than 1 DMX univers
Statistics: Posted by martignasse — 15 Jan 2016, 18:57
]]>