ArrayArrayArrayArrayArrayArrayArrayArray BrainModular BrainModular Users Forum 2017-09-20T11:31:02+02:00 https://brainmodular.fr/forums/app.php/feed/topic/5611 2017-09-20T11:31:02+02:00 2017-09-20T11:31:02+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=37797#p37797 <![CDATA[SDK multi callbacks still have problems]]> I'll implement some changes in the SDK, especially in the
onMouseUpMulti, onMouseMoveMulti,onMouseDownMulti

for example :
onMouseUpMulti (TMouseButton MouseButton, TShiftState Shift, UsineEventPtr X, UsineEventPtr Y, UsineEventPtr MouseDownArray)

It will do the trick and keep the backward compatibility.

Statistics: Posted by senso — 20 Sep 2017, 11:31

]]> 2017-07-15T03:18:19+02:00 2017-07-15T03:18:19+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=37375#p37375 <![CDATA[SDK multi callbacks still have problems]]> For example,
virtual void onMouseUpMulti (TMouseButton MouseButton, TShiftState Shift, UsineEventPtr X, UsineEventPtr Y)

The X and Y are arrays with an entry for each touch point that is being tracked.
But MouseButton is just left, right or middle button.
So you know a touch point has Up, but not which one.

Similar problem for onMouseDownMulti.

A MouseDown array event needs to be added so we know the up/down state of each of the touch points.

It could really be a new callback such as:
onMouseButtonMulti(UsineEventPtr UpDownArray, TShiftState Shift, UsineEventPtr X, UsineEventPtr Y)

The user can track which touchpoint's button has changed state by storing the previous values.
Note that several buttons may have changed state at the same time, so it should not be assumed that each callback is only informing about 1 button.

If the callback is to indicate which button is pressed you need 3 state arrays, one for each button. Note that the module parameters do no distinguish between the buttons.

Alternatively the SDK could guarantee to callback separately for each button changed, and just indicate the touchpoint number and state of the button that has been pressed. Then arrays would not be required.

Anyway, please can this be fixed soon.

Simon.

Statistics: Posted by sm_jamieson — 15 Jul 2017, 03:18

]]> 2016-12-22T16:39:55+02:00 2016-12-22T16:39:55+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36518#p36518 <![CDATA[SDK multi callbacks still have problems]]>
Using the touch screen, I am getting continuous mouse multi 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.

Statistics: Posted by sm_jamieson — 22 Dec 2016, 15:39

]]> 2016-12-21T18:19:30+02:00 2016-12-21T18:19:30+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36495#p36495 <![CDATA[SDK multi callbacks still have problems]]> Statistics: Posted by senso — 21 Dec 2016, 17:19

]]> 2016-12-21T17:24:23+02:00 2016-12-21T17:24:23+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36490#p36490 <![CDATA[SDK multi callbacks still have problems]]> Statistics: Posted by 23fx23 — 21 Dec 2016, 16:24

]]> 2016-12-21T16:31:59+02:00 2016-12-21T16:31:59+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36488#p36488 <![CDATA[SDK multi callbacks still have problems]]> MouseMoveMulti
MouseDownMulti
MouseUpMulti

procedures ?

you should get precise info with those procedures.

Statistics: Posted by senso — 21 Dec 2016, 15:31

]]> 2016-12-08T17:37:52+02:00 2016-12-08T17:37:52+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36398#p36398 <![CDATA[SDK multi callbacks still have problems]]> Statistics: Posted by 23fx23 — 08 Dec 2016, 16:37

]]> 2016-12-08T12:43:49+02:00 2016-12-08T12:43:49+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36396#p36396 <![CDATA[SDK multi callbacks still have problems]]>
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 !

Also, 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.

I hope this can be fixed at least in HH3 SDK.

Thanks,
Simon.

Statistics: Posted by sm_jamieson — 08 Dec 2016, 11:43

]]> BrainModular BrainModular Users Forum 2017-09-20T11:31:02+02:00 https://brainmodular.fr/forums/app.php/feed/topic/5611 2017-09-20T11:31:02+02:00 2017-09-20T11:31:02+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=37797#p37797 <![CDATA[SDK multi callbacks still have problems]]> I'll implement some changes in the SDK, especially in the
onMouseUpMulti, onMouseMoveMulti,onMouseDownMulti

for example :
onMouseUpMulti (TMouseButton MouseButton, TShiftState Shift, UsineEventPtr X, UsineEventPtr Y, UsineEventPtr MouseDownArray)

It will do the trick and keep the backward compatibility.

Statistics: Posted by senso — 20 Sep 2017, 11:31

]]> 2017-07-15T03:18:19+02:00 2017-07-15T03:18:19+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=37375#p37375 <![CDATA[SDK multi callbacks still have problems]]> For example,
virtual void onMouseUpMulti (TMouseButton MouseButton, TShiftState Shift, UsineEventPtr X, UsineEventPtr Y)

The X and Y are arrays with an entry for each touch point that is being tracked.
But MouseButton is just left, right or middle button.
So you know a touch point has Up, but not which one.

Similar problem for onMouseDownMulti.

A MouseDown array event needs to be added so we know the up/down state of each of the touch points.

It could really be a new callback such as:
onMouseButtonMulti(UsineEventPtr UpDownArray, TShiftState Shift, UsineEventPtr X, UsineEventPtr Y)

The user can track which touchpoint's button has changed state by storing the previous values.
Note that several buttons may have changed state at the same time, so it should not be assumed that each callback is only informing about 1 button.

If the callback is to indicate which button is pressed you need 3 state arrays, one for each button. Note that the module parameters do no distinguish between the buttons.

Alternatively the SDK could guarantee to callback separately for each button changed, and just indicate the touchpoint number and state of the button that has been pressed. Then arrays would not be required.

Anyway, please can this be fixed soon.

Simon.

Statistics: Posted by sm_jamieson — 15 Jul 2017, 03:18

]]> 2016-12-22T16:39:55+02:00 2016-12-22T16:39:55+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36518#p36518 <![CDATA[SDK multi callbacks still have problems]]>
Using the touch screen, I am getting continuous mouse multi 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.

Statistics: Posted by sm_jamieson — 22 Dec 2016, 15:39

]]> 2016-12-21T18:19:30+02:00 2016-12-21T18:19:30+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36495#p36495 <![CDATA[SDK multi callbacks still have problems]]> Statistics: Posted by senso — 21 Dec 2016, 17:19

]]> 2016-12-21T17:24:23+02:00 2016-12-21T17:24:23+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36490#p36490 <![CDATA[SDK multi callbacks still have problems]]> Statistics: Posted by 23fx23 — 21 Dec 2016, 16:24

]]> 2016-12-21T16:31:59+02:00 2016-12-21T16:31:59+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36488#p36488 <![CDATA[SDK multi callbacks still have problems]]> MouseMoveMulti
MouseDownMulti
MouseUpMulti

procedures ?

you should get precise info with those procedures.

Statistics: Posted by senso — 21 Dec 2016, 15:31

]]> 2016-12-08T17:37:52+02:00 2016-12-08T17:37:52+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36398#p36398 <![CDATA[SDK multi callbacks still have problems]]> Statistics: Posted by 23fx23 — 08 Dec 2016, 16:37

]]> 2016-12-08T12:43:49+02:00 2016-12-08T12:43:49+02:00 https://brainmodular.fr/forums/viewtopic.php?t=5611&p=36396#p36396 <![CDATA[SDK multi callbacks still have problems]]>
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 !

Also, 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.

I hope this can be fixed at least in HH3 SDK.

Thanks,
Simon.

Statistics: Posted by sm_jamieson — 08 Dec 2016, 11:43

]]>