Integer rounding

[Vocaleyes]

Would anyone with the know how be able to tell me if this https://support.microsoft.com/en-us/off ... 308e403748 has any place in the current state of mouse handling techniques, or if that’s the wrong thing entirely, essentially looking to see if integer rounding is used in mouse cursor positioning, please and thank you.

[Vocaleyes]

Looking more into this, touchscreen input seems unaffected by this drifting bug.

So I wonder if it’s due to this;

GMMP_USE_DISPLAY_POINTS 1 - Retrieves the points using the display resolution.

whereas GMMP_USE_HIGH_RESOLUTION_POINTS 2 - Retrieves high resolution points. Points can range from zero to 65,535 (0xFFFF) in both x- and y-coordinates. This is the resolution provided by absolute coordinate pointing devices such as drawing tablets.

Could explain why dpi scaling is hit and miss or in my case why scaling display exacerbates this issue.

How would one check to see if mouse is indeed using gmmp 1 and would it be a good idea/ possible to use 2?

https://learn.microsoft.com/en-gb/windo ... dfrom=MSDN

[Vocaleyes]

Issue was resolved on Mac by switching from integer to floating point.

https://github.com/symless/synergy-core/pull/6469

Merged with another report of my specific drift, up and to the left.

https://github.com/input-leap/input-leap/issues/112

Does windows use int instead of float? And how to change. Thanks.

[Vocaleyes]

This can be closed if needed. It has been confirmed that the drift isn’t due to how the coordinates are being calculated.

[Shade7]

This can be closed if needed. It has been confirmed that the drift isn’t due to how the coordinates are being calculated.

Any info on what the real cause of the drift is?

[Vocaleyes]

Not as of yet, only that the drift is observable through submitted input data. But for the first time in years am hopeful.

[Shade7]

Not as of yet, only that the drift is observable through submitted input data. But for the first time in years am hopeful.

Keep us updated- I'm intereted in finding out.