Views: 6,695,730 Homepage | Main | Rules/FAQ | Memberlist | Active users | Last posts | Calendar | Stats | Online users | Search 03-28-24 11:08 AM
Guest:

0 users reading Please separate Save and Load under File Menu | 1 bot

Main - General - Please separate Save and Load under File Menu Hide post layouts | New reply


VeryStupidBitfield
Posted on 02-09-23 11:29 PM Link | #5835
TLWontRead; Put Load State Above Save State. L comes before S, you usually want to load before you want to save, you usually this would make sense.

Mostly useless context and additional useless suggestions:

Hi. I love melonDS, we are a couple who is firing up an emulator for the first time in many years. I can't believe how feature rich melonDS is.
Our favorite feature is the Auto window priority, so curious how that's done, for the games pkmn silv&plat it's perfect every time. Wonder if developers set DS screen priority for most menus or something?

Anyway, I'm here because twice now my wife has accidently saved over state 1 when booting the game up twice now. This is completely our human error and I'm not at all here to complain. In fact I did fork and build it my self but I don't know anything about qt, I couldn't even add a separator or put save at the bottom of the menu, and I don't want to go through a trial of qt to use creator, so I am just going to leave some feedback, please note this also isn't for melonDS specifically as this is standard for all emulators.

My (personal) Problem: Save State is too easy to press. Most the time you must mouse over Save State to get to Load State.

Possible imo solutions in order from least to most PIA:

1. Put Load State Above Save State. L comes before S, you usually want to load before you want to save, you usually this would make sense.

2. Separate Save State and Load State, add some options

3. Check if melonDS has been open for >30 seconds and if so, have at least 5 inputs have been received. If this case is false, prompt "save over state 1?". Some kind of case to add a prompt to prevent accidents

3. Make a new option based on the behavior of "Separate Save States" where when true, OnSaveState creates brand new .sav (and .md# files?) So I can have the option to have a file history as a makeshift source control solution. When enabling this, it still writes over each save state.

Cheers!

Nadia
Posted on 02-09-23 11:37 PM Link | #5836
I'd recommend that you just don't load a state to continue the game right after opening the emulator. Use in game saves and only make save states if you want to use them as a snapshot to retry something - that way you'll save yourself from inevitable data loss.

VeryStupidBitfield
Posted on 02-14-23 11:51 PM Link | #5849
Your preaching to the choir here. This is just a UX suggestion. Based on my how my wife, the majority of downloaders, would use it and what others are probably accidently experiencing and not reporting. A small change of switching the order the menu elements are created could make a huge difference to people who refuse to change their process and workflow (my wife)

patataofcourse
Posted on 02-14-23 11:57 PM Link | #5850
savestates will break between versions, if you keep using them you're either gonna a. have to stick to an older melon version anyway b. restart your game c. actually use the ingame save functionality


____________________
hi
they/she/xe :))))))))))))))


Main - General - Please separate Save and Load under File Menu Hide post layouts | New reply

Page rendered in 0.030 seconds. (2048KB of memory used)
MySQL - queries: 27, rows: 82/82, time: 0.018 seconds.
[powered by Acmlm] Acmlmboard 2.064 (2018-07-20)
© 2005-2008 Acmlm, Xkeeper, blackhole89 et al.