-
Notifications
You must be signed in to change notification settings - Fork 1
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
[Feature Request]: Slight improvement #8
Comments
I actually didn't mean to place the Use Per-game configs checkbox to where it is now, I just messed up the code and didn't care enough to fix it as long as it was a in sort of okay place lol. Presets and a Welcome screen are not a bad idea, but first I'd like to reach a conclusion with everyone else about how the final GUI will look like, and until then I don't really want to add a lot to this as it will get overridden anyway (see shadps4-emu#2311 for that), but once that is settled, we can come back to these. There were also some comments about changing the Default button's behaviour to always reset the config to the builtin default, which I didn't really like as it offers no alternative to the current functionality, but your suggestion to add presets would solve the issue rather neatly, especially if the user also had the ability to create their own presets as well, I'll also add that to the list of things to do after the GUI is finalized. |
I think you also need to develop your GUI further, because it's very good. The new graphical interface is unknown when it will be ready, but in the future, your interface will be a kind of backdoor. I believe that the user should have a choice, so even if a new interface is created, I would like yours to remain at least as a separate button, such as "manual editing", where you can assign multiple buttons to a single action and make other edits. Now I'll tell you about the presets in my understanding for your interface. I'll take Bloodborne as an example.
IMPORTANT: The emulator must remember that the soulsborne preset was used for this file (CUSA03173.ini). If you are playing [CUSA08632] Call of Duty®: WII, for example (found in the compatibility database), then you have the shooter preset applied and the reset will occur to the shooter preset. |
My idea is something that's a bit different: There would be a Presets button in the place of the Default button, that would bring up its own submenu, where you have the following options:
The presets list would initially only contain the built-in default config, making this the new way to reset to the original settings. I don't think that remembering what preset to reset a config to would be worth implementing in this system, as it's already something you can achieve with this setup with just a few more clicks. |
I'll duplicate the text:
-Gaming Preset- -Editing Presets- *Default.ini can be made not as a configuration file, but as a preset, selecting which will display the control that is currently installed (keyboard only). P.S. I seem to have made all the changes I wanted, but there may be errors and flaws in the text, but as for the interface itself, everything seems to be correct, so I think this is the final version of my vision of your GUI for greetings and presets. |
Checklist
Description
@kalaposfos13 I suggest you make your interface a little more friendly for beginners.
Remove default.ini from the configuration selection and replace it with hello.ini with the text as shown in the screenshot.
hello.ini will be displayed in the list as CUSAXXXX.
Rename the "Default" button to "Reset", it will also reset the file to default.ini, but the hello.ini file should be an exception.
I also had thoughts about presets for configurations like "Shooter", "Soulsborne" and so on.
This is separate from the configuration files. But you probably won't want to add it.
Reason
The interface is more friendly for beginners.
Also, the "Use Per-Game config" has a more convenient location, which will also be better for translations into other languages.
Examples
The text was updated successfully, but these errors were encountered: