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

Windows tablet (z8300) cannot scroll down since v1.3-918-ge17772b #9554

Closed
sum2012 opened this issue Apr 4, 2017 · 23 comments
Closed

Windows tablet (z8300) cannot scroll down since v1.3-918-ge17772b #9554

sum2012 opened this issue Apr 4, 2017 · 23 comments
Milestone

Comments

@sum2012
Copy link
Collaborator

sum2012 commented Apr 4, 2017

@unknownbrackets
That mean #9430
User report from baidu

@hrydgard
Copy link
Owner

hrydgard commented Apr 4, 2017

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.

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 5, 2017

He tell me that use touch to scroll

@unknownbrackets
Copy link
Collaborator

unknownbrackets commented Apr 5, 2017

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]

@hrydgard
Copy link
Owner

hrydgard commented Apr 5, 2017

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.

hrydgard added a commit that referenced this issue Apr 5, 2017
Allow using any touchId to scroll. Should help #9554.
@hrydgard
Copy link
Owner

hrydgard commented Apr 5, 2017

That change should fix it up.

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 5, 2017

I will give him try

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 5, 2017

He tell me v1.4-43, the touch point is not correct.
For example.click "Setting" ,ppsspp pop up "Load ..." in the menu.
This is no problem in v1.3

@hrydgard
Copy link
Owner

hrydgard commented Apr 5, 2017

OK, strange.. Might be related to the DPI fixes. I'll check and see if I find something obvious.

hrydgard added a commit that referenced this issue Apr 5, 2017
@hrydgard
Copy link
Owner

hrydgard commented Apr 5, 2017

I found something, at least. Please test again :)

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 5, 2017

I tell him test again.
One other thing,this issue of Milestone should be mark as v1.5 or v1.4.2 ?

@hrydgard hrydgard added this to the v1.4.1 milestone Apr 5, 2017
@hrydgard
Copy link
Owner

hrydgard commented Apr 5, 2017

Not sure if I'll release a 1.4.1 or go directly to 1.5. 1.4 has some bugs like this though..

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 5, 2017

He has another problem on ppsspp on UI.
But I want to solve this first.
So that we don't confuse.

@hrydgard
Copy link
Owner

hrydgard commented Apr 5, 2017

Sounds resonable. Now, did this last change work?

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 6, 2017

Thanks ,He test on v1.4-48 ,fixed touch point ,closing this issue,I will open another issue for other UI problem

@sum2012 sum2012 closed this as completed Apr 6, 2017
@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 6, 2017

He said that top to down scroll still not fix
So I reopen

@sum2012 sum2012 reopened this Apr 6, 2017
@unknownbrackets
Copy link
Collaborator

unknownbrackets commented Apr 6, 2017

Maybe here too?

info[0] = pointers[0].lastX - pointers[0].downX;

-[Unknown]

@hrydgard
Copy link
Owner

hrydgard commented Apr 6, 2017

Oh, indeed. I'll fix that too.

@hrydgard
Copy link
Owner

hrydgard commented Apr 6, 2017

Committed another fix, I believe this should work now.

Thanks @sum2012 + friend for all the testing.

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 6, 2017

Unlucky V1.4-50 still not fix top to down scroll

@hrydgard
Copy link
Owner

hrydgard commented Apr 6, 2017

Sigh, of course, I forgot an important detail... hang on.

hrydgard added a commit that referenced this issue Apr 6, 2017
@hrydgard
Copy link
Owner

hrydgard commented Apr 6, 2017

@sum2012 hopefully that will do it. sorry :)

@hrydgard
Copy link
Owner

hrydgard commented Apr 6, 2017

And one more to fix bugs from that one :)

@sum2012
Copy link
Collaborator Author

sum2012 commented Apr 7, 2017

Thanks v1.4-52 fix top to down scroll
Remain #9563 problem
Closing

@sum2012 sum2012 closed this as completed Apr 7, 2017
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

3 participants