SDK mouse multi callbacks

[sm_jamieson]

In the SDK multi callbacks are now working at last - excellent.
However I have noticed that when then touch screen is being used, the Mouse Move Multi callback is called continuously with the same x and y value when a finger is in one position on the screen. This can be filtered out by storing the previous value and only processing changed values.
But it is not very efficient as the SDK function is being called a huge number of times.
Maybe the touch point values reported by Windows to Usine are changing all the time at a very low level, but these should be filtered out by Usine.
This problem does not occur when with the X and Y module parameters - when the finger is still, the values to not change.
Please can we change the SDK mouse callbacks to only report changes in the value (down to some minimum resolution).

I will check for the non "Multi" callbacks tomorrow - I'm not sure if they behave the same way or not.

[senso]

not sure:
the callback is almost called directly by the Windows API. The continuous call can give interesting info like "fingers are still in touch" which can be very interesting. Internally, in Usine we use it a lot.
So I can't take such a decision and filter duplicated messages.

The best soluce is to filter messages in your user module?

[sm_jamieson]

OK I understand. I already filter in my module.
Thanks.