-
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
Redesign pause screen UI - ideas here #13016
Comments
IMHO it's better to have save/load button and only after the slot selection: if one miss-click can still cancel any action, also this will have 2 button on main screen and leave the 5 to the bigger popup. It's possible to select the wrong slot but the worst case is to overwrite the wrong one (if a user want to keep one safe could still probably use like the 5th slot and only the first for other making them further away), still way better than to load when you want to save or viceversa. |
Personally never liked the Save State/Load State repetition on the pause screen, but I don't think it needs a mayor redesign like proposed above. I recall we already had an issue about the missclick on android problem and recall my idea was to move it out to savestate preview screen. Save and load could simply be removed and keep the Save and Load on the bottom of image preview while Undo on the upper right of it. "Back" could be removed from preview dialog and just clicking on the image or anywhere outside of the preview window would leave the dialog without having to choose the option. An empty slot could have a "save" in place of the miniature to point the users where they should be clicking. |
Right, as LunaMoo mentioned - this is exactly the same as #7437 and we should keep just one. IMHO, it's nice seeing which save states are available at a glance. Personally, I'd prefer the confirmation/buttons inline. For example, first it shows:
If you tap the image, the same thing that happens now would happen. If you tap the rest, it'd slide in:
But we could also keep the buttons and show a confirmation in the same way. While thinking about this UI, it'd be nice to introduce an "Undo" button for saves made recently (we currently save the file, only on desktop, but there's no real UI for it.) We could even save state to a temp slot before loading, and allow an undo. I think that would fully address the misclick problem. That said, it can just be in the dialog and I think that'd be okay too. -[Unknown] |
I would appreciate the addition of a button that exits to desktop. In one of my setups,the most convenient way to close the emulator is by exiting to the menu, then exiting to desktop, and I'd like it if I could close PPSSPP in one menu instead of two. |
One other thing I want to do is a "transparent" mode where you can edit post processing settings and aspect ratio etc and immediately see the effects, on the paused game - the controls would hover over the screen. I'm imagining an "Display settings" button on the page screen that switches it to such a mode. |
We now have transparent background, and the post processing stuff is handled in separate issues. Moving further improvements here to 1.15. |
#16593 |
#16398 |
Yeah, true. Maybe should have put them in the other order? Not sure what people do the most often. If you have ideas, do post them. |
Maybe add an additional option to switch position "Savestate" and "Loadstate"? |
Or maybe move the small save image to the center and the button to the side, I'm not sure if it will look ugly. After a day of use, I found the issue to be not entirely unacceptable, currently the SL only needs a little extra hand movement. |
Currently it's way too easy to misclick, because to handle 5 save states on-screen we've had to make the save/load state buttons too small.
Floe proposed the following UI (clickable mockup: https://app.moqups.com/NKxxdPt3AY/view/page/ad64222d5 ) where you first click whether to save or load, then click the state.
There are many other possibilities though, like first click the slot, then save/load, for example. Not sure what's safest against misclicks. Maybe even easy access to an Undo Save State function would be a reasonable workaround...
The text was updated successfully, but these errors were encountered: