The documentation makes it appear as if one can achieve accurate mouse movement with it.
|
interception.mouse_position() |
|
>>> 300, 400 |
|
|
|
# move the mouse by 100 pixels on the x-axis and 0 in y-axis |
|
interception.move_relative(100, 0) |
|
interception.mouse_position() |
|
>>> 400, 400 |
It seems that the actual number of pixels moved is dependent also on the mouse speed setting (based on the info here https://github.com/learncodebygaming/pydirectinput/blob/a585d044aed678576fefd24e7ad0c5945ab52366/pydirectinput/__init__.py#L412C7-L417). In my tests it has moved more pixels than I've called move_relative with.
I suggest to update the documentation.
The documentation makes it appear as if one can achieve accurate mouse movement with it.
pyinterception/src/interception/inputs.py
Lines 110 to 116 in 0da18c0
It seems that the actual number of pixels moved is dependent also on the mouse speed setting (based on the info here https://github.com/learncodebygaming/pydirectinput/blob/a585d044aed678576fefd24e7ad0c5945ab52366/pydirectinput/__init__.py#L412C7-L417). In my tests it has moved more pixels than I've called move_relative with.
I suggest to update the documentation.