Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the actual move offset does not match ipad resolution pixel #50

Open
memetea opened this issue Apr 20, 2023 · 1 comment
Open

the actual move offset does not match ipad resolution pixel #50

memetea opened this issue Apr 20, 2023 · 1 comment

Comments

@memetea
Copy link

memetea commented Apr 20, 2023

I tested on ipad mini 5. The resolution is 2048*1536.
1、When I set initial x to 0 and call move to increment x by 10 every time. I found that x incremented by about 1300 totally when the cursor reaches the edge of screen in landscape view. That's far away from 2048.
2、When changing increment step from 10 to 50. The final movement along x axis is only about 660.
3、When calling simpleMove(0,0) #19 and then moveTo(0, 100, 1.0, 0, 0, 0) the cursor moves along y by y1. When calling simpleMove(0,0) and followed by moveTo(100, 100, 1.0, 0, 0,0) the cursor moves along y by y2. I found that y1 is larger than y2.

I don't understand why the above experiments happen. Is there any explaination?
Thanks in advance.

@memetea
Copy link
Author

memetea commented Apr 22, 2023

It seems there are acceleration that cause the logical movement does not equal to physical movement.
Moving 100 three times and moving 300 once along x direction does not go to the same physical point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant