Ask before saving to and loading from a global state

[ghost]

Because both "Save global state" and "Load global state" are NEXT TO each other in the File menu AND they are both SMALL in the screen, there is a BIG chance and probability that the user will both accidentally and mistakenly "Save global state" instead of "Load global state" and vice versa when his or her hand SLIPS!

So my idea, proposal and suggestion is to ask the user the following question:

Are you sure that you want to save to global state?

Every time the user wants to "Save global state"

AND

Are you sure that you want to load from global state?

Every time the user wants to "Load global state"

NOTE:

No dialog appears if the user saves and loads states to and from slots, Not even if he or she quickly saves or loads a state by pressing a key on his or her keyboard because the slots menus are designed in a way so the chances and probabilities for an accident and a mistake are too small and the keyboard is used to quickly save and load a state and a dialog will make it both not quick and annoying.

These two dialogs are only for "Save global state" and "Load global state" specifically!

Is that clear? If yes then what do you think about this idea? I am will be glad to hear your opinions!

Optionally you can add a new checkbox so the user can choose to not show these dialogs even for "Save global state" and "Load global state"

[wheremyfoodat]

But like, you need to spawn the top menu bar, press the file button, and then click one of those options to do it. I can't see many people doing it accidentally.

[ghost]

But like, you need to spawn the top menu bar, press the file button, and then click one of those options to do it. I can't see many people doing it accidentally.

I played Final Fantasy XIV/14 yesterday and there is a duty that must be done in order to proceed with the main story.

I tried to register to that duty but accidentally registered to other duty and commenced which I have already done before and I didn't had to repeat that duty at all.

Since players cannot leave any duty without any penalties after commence I had to do it again from the beginning to the end and wasted both time and energy.

This accident happened because the story of Final Fantasy XIV/14 is very interesting and my mind was busy on thinking about what will happen next in that very interesting story before I proceed and didn't notice that I accidentally selected the wrong duty in the duty finder window.

Many PS1 games are not less interesting than Final Fantasy XIV/14, especially Final Fantasy VII/7, VIII/8 and IX/9, and the accident to click "Load global state" instead of "Save global state" in the File menu of PCSX-Redux PlayStation one emulator is much more likely than what you both think and believe.

Also think how much bad it is if this accident happens to someone while he or she is playing a very hard survival horror game with a very interesting story, like Resident Evil, which also greatly limits the player on saving his or her progress to the memory cards and the user will probably want to heavily use the save state feature of the emulator to save his or her progress whenever he or she wants to, if he or she is a casual player, and think about what will happen next in the game and story at the same time and not notice whether or not he or she clicks "Save global state" or "Load global state" at all.

Either ask before "Save global state" and "Load global state" or at least completely remove both "Save global state" and "Load global state" from the File menu of PCSX-Redux PlayStation one emulator because at their current state they can devastate their users and they are unnecessary since their progress can always be saved to a slot, quick and sometimes to the memory cards too which are more safe to use than the global state.

[NDR008]

Use a different emulator?

[ghost]

Use a different emulator?

Unfortunately only PCSX-Redux provides all the tools, utilities and features that a cheater and hacker like me needs like Memory Observer Delta-Over-Time search, Memory Read and Write Breakpoints, Memory Editors and etc.

If DuckStation would at least allow me to add and use memory read and write breakpoints like PCSX-Redux does, because DuckStation already has a memory scanner with a feature to freeze any memory address exactly like Cheat Engine, then I would consider to use DuckStation instead.

Even if either Nymashock or Octoshock PS1 cores of Bizhawk had a working debugger then I would use Bizhawk instead of PCSX-Redux but unfortunately neither Nymashock nor Octoshock have a working debugger because Bizhawk also has a memory scanner with the freeze feature exactly like DuckStation does.

Anyway I am just telling you my recent experience and opinions in my life. That's all and if I will have more examples and instances in the future about this subject or topic then I will not hesitate to report them here too to both bold and emphasis the importance of this feature request.

All the collaborators and developers of the PCSX-Redux project are still free to work on what they think is most important now.

Meanwhile I am saving my progress to a slot, neither global (because as I said earlier both save and load are next to each other in the File menu and they both don't ask on click) nor quick (because they are bound to F1 and F2 respectively which are next to each other on the keyboard) nor memory cards (because I can't always save my progress with them), which is more safe while benefiting from all the debug tools and utilities that PCSX-Redux currently provide me and this is okay for me for now.

I am a software quality assurance user and I will keep reporting any new issue here that I will find in the future with PCSX-Redux in order to contribute and improve this excellent PlayStation one emulator.

All what I want to know if you really know the problem that I am describing here?

[NDR008]

Don't worry we understood you the first time.
You sometimes clicked on the wrong item from the menu, and it caused you a lot of personal suffering.
But we would prefer you do not keep adding more comments about the same topic.

[ghost]

Don't worry we understood you the first time. You sometimes clicked on the wrong item from the menu, and it caused you a lot of personal suffering. But we would prefer you do not keep adding more comments about the same topic.

I am glad to hear that and I will listen to you and do as you say.