-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Windows tablet (z8300) cannot scroll down since v1.3-918-ge17772b #9554
Comments
This is when using touch, I assume? Maybe we aren't properly sending touch move events while touch is held down on Windows, or something... Touch works through the UWP APIs but we use a different path for touch in the desktop version. |
He tell me that use touch to scroll |
Ah. I see it: if ((input.flags & TOUCH_DOWN) && input.id == 0) {
scrollStart_ = scrollPos_;
inertia_ = 0.0f;
} Only input.id == 0 is allowed to scroll. To avoid clashes the code is skipping the mouse id (0), because the code had a comment indicating it was doing something to avoid interfering with the mouse (even though it looked broken.) https://github.com/hrydgard/ppsspp/pull/9430/files#diff-c3532e1a49254f9d8a00e53675aa251aR50 We can probably change this to 0, probably unlikely people will touch and use a mouse simultaneously. But I wonder if scrolling only for touch.id == 0 is best or not... -[Unknown] |
I think the idea for the ==0 check was to avoid multiple simultaneous touches interfering with each other. It might also be viable to grab a touchID on touch down, and ignore all other touch events in that scrollview until that touch has been released. That would also make it possible to scroll two views simultaneously with different fingers which I guess would be kinda cool. |
Allow using any touchId to scroll. Should help #9554.
That change should fix it up. |
I will give him try |
He tell me v1.4-43, the touch point is not correct. |
OK, strange.. Might be related to the DPI fixes. I'll check and see if I find something obvious. |
I found something, at least. Please test again :) |
I tell him test again. |
Not sure if I'll release a 1.4.1 or go directly to 1.5. 1.4 has some bugs like this though.. |
He has another problem on ppsspp on UI. |
Sounds resonable. Now, did this last change work? |
Thanks ,He test on v1.4-48 ,fixed touch point ,closing this issue,I will open another issue for other UI problem |
He said that top to down scroll still not fix |
Maybe here too? ppsspp/ext/native/input/gesture_detector.cpp Line 100 in 2019542
-[Unknown] |
Oh, indeed. I'll fix that too. |
Committed another fix, I believe this should work now. Thanks @sum2012 + friend for all the testing. |
Unlucky V1.4-50 still not fix top to down scroll |
Sigh, of course, I forgot an important detail... hang on. |
@sum2012 hopefully that will do it. sorry :) |
And one more to fix bugs from that one :) |
Thanks v1.4-52 fix top to down scroll |
@unknownbrackets
That mean #9430
User report from baidu
The text was updated successfully, but these errors were encountered: