-
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
Default controls.ini currently makes touchpad 'analog stick' if there is no controller available #11139
Comments
Bump. This is still happening, dragging the touchpad anywhere into the left side of a submenu is enough to get the submenu closed in ppsspp. the console says this interesting thing:
I removed the 'auto assigned' mappings the the touchpad and things started working correctly, but the point such as it is, is that a touchpad should probably not be confused with a controller on first startup. |
Also something that's quite bad usability happens too: F1 is the key to open the 'help' (this actually opens the browser and sends you to the site even if the browser is closed). Since this is right next to 'esc' which is used to open the menu and there appears to be no way to unmap this (unnecessary) shortcut, this is quite annoying. |
Hm, I guess that's Qt specific? Windows doesn't do that on F1. I guess we should remove the touchpad from the gamecontrollerdb? -[Unknown] |
Yeah I doubt it happened before QT. I'm a bit clumsy and it never did before it became default. edit: if you click on the help menu while windowed in linux you'll see two 'default' shortcuts, one for the official site (F1) and another for 'about ppsspp' (shift+F1). |
Oh, btw i've seen this happening in other applications too. I don't know if it's a sdl, qt, wx or gnome problem (i'm pretty confused about what fs-uae-launcher uses) but in that application it's pretty explicit - if you have any game config selected the default config for 'amiga joystick' if you don't have a controller yourself is 'Default (SynPS/2 Synaptics TouchPad)'. Which sounds super wrong, and sure enough causes problems. |
So, this is still happening. It manifests on a newly downloaded buildbot build ( v1.7.5-403-g128c0ad ). Which is quite old, but its probably the youngest one if i don't want to build, which i don't. The ppa is abandoned. To reproduce, i just click on 'settings' and move the mouse. Instant exit from 'settings' back into the main. I probably should wait to see if #12173 (comment) which was just merged changes the issue, but here are the config files anyway:
|
You don't have anything mouse related mapped in your control mapping - 1 = keyboard and 10 = generic gamepad which I assume is your touchpad - so no, the merged PR should not affect you in any way. If you think touchpad is mapped in a really awful way like direction ends up as circle which causes pressing that direction to leave menus in the UI, you can provide better mapping for said touchpad through gamecontrollerdb.txt(can be edited by for example this tool, it could also be completely removed from that file as [Unknown] proposed above, but that will make it completely unusable for PPSSPP. If it's also detected as mouse it might become usable after some linux user implements mouse control for that OS, but there's not that many contributors from Linux so it might not happen anytime soon. |
No rush actually, i'm using retroarch version, which doesn't have this problem (not sure if it would exist if the internal UI existed in the libretro version, but it doesn't). I'm just notifying you so you're aware that this problem still exists and if you spotted something. I'm actually surprised no one else confirmed it. Maybe it's something that only happens in wayland or everyone simply uses gamepads. I find it really weird. I 'know' it's a mapping from the analog controls, because if i start a game that uses them (in this case the 3rd birthday) i can move the character with the touchpad, which is something i never actually configured ( i use the keyboard for everything ). Anyway, thanks for linking that tool, it's SDL2 fault then... couldn't this particular situation in PPSSPP be avoided by making sure that the 'controller' is not mapped to the same device as the mouse in the UI and giving priority to the mouse when they conflict? I don't actually mind the analog mapping to the only 'analog' device on the keyboard in games. |
I guess we could search for "TouchPad" in the name of detected mappings and deny them? Sounds like this is actually a mapping not currently in gamecontrollerdb - just being autodetected by SDL2 wrong. Not sure if there's some flag that comes back that this isn't really a controller. I don't know that we get a device. See here: Lines 53 to 67 in aa927e0
Please note that -[Unknown] |
Is this still happening, should we do something about it? This is the only instance of this issue I've ever heard about, never even seen it in my email flood. |
I changed portable (the other died) and i'm not using standalone ppsspp anymore, so you can close this if you can't reproduce. It was really frustrating though. Just imagine trying to navigate the menus and every time you moved the cursor there was a 80% chance of having a submenu closed on the savestate menu. |
Yeah I can imagine, but it's gotta be rare. Unlikely to work on this unless it comes up again though, so closing. |
What happens?
Pretty much what's on the title. This is a 'problem' for people without controllers because they use the mouse to navigate the menus. Only, natch, some 'directions' of the touchpad serve to exit menus (didn't bother to check which). Which means every time they move the mouse to click on the buttons there is a chance to exit the submenu.
What should happen?
Dunno, maybe filter touchpad from 'analog' device candidates or don't apply them in the menu as mouse pointer controller and analog stick at the same time.
What hardware, operating system, and PPSSPP version? On desktop, GPU matters for graphical issues.
linux x86-64 Wayland ubuntu bionic.
The text was updated successfully, but these errors were encountered: