feature request: bind a key to save/load directly state X
Moderator: ZSNES Mods
feature request: bind a key to save/load directly state X
instead of using state shortcuts to select the state X for save/load let me bind a key (e.g. F2) to save directly to slot 2 and other key to load directly from slot 2 (e.g. F4)
-
- ZSNES Developer
- Posts: 6747
- Joined: Tue Dec 28, 2004 6:47 am
I don't see the problem, direct saves/loads don't have to be binded by default at all if you fear that this would lead zsnes users to not using all 100 states per game.Deathlike2 wrote:You do realize the number of buttons that would be needed for this?
Intelligent usage of the existing feature is the way to go, particular when there are 100 states, not just 10 states.
-
- Regular
- Posts: 271
- Joined: Tue Jun 14, 2005 8:35 pm
I rarely find the use for more than two or three save states per game. For me it would be more convenient to directly save to the preferred slot since I utilize much less than 100 save/load states.Truth Unknown wrote:...Adept, don't you think you are over thinking the need for such customizations? Is it really that hard to push F3 (Default) to change a slot to Save (F2 by Default) or Load (F4 by Default)?
-
- Regular
- Posts: 271
- Joined: Tue Jun 14, 2005 8:35 pm
-
- ZSNES Shake Shake Prinny
- Posts: 5632
- Joined: Wed Jul 28, 2004 4:15 pm
- Location: PAL50, dood !
I *hate* shift+Fn for saving. Which is about the only way to make it work.
H
A
T
E
If you can think of a proper way to quickload/save that's actually quick and does the "one key per slot", feel free to share.
H
A
T
E
If you can think of a proper way to quickload/save that's actually quick and does the "one key per slot", feel free to share.
皆黙って俺について来い!!
Pantheon: Gideon Zhi | CaitSith2 | Nach | kode54
Code: Select all
<jmr> bsnes has the most accurate wiki page but it takes forever to load (or something)
the proper way to implement this direct save/load state feature is complete freedom to bind whatever keys user prefers. that's about it.grinvader wrote:I *hate* shift+Fn for saving. Which is about the only way to make it work.
H
A
T
E
If you can think of a proper way to quickload/save that's actually quick and does the "one key per slot", feel free to share.
-
- ZSNES Developer
- Posts: 6747
- Joined: Tue Dec 28, 2004 6:47 am
The simple hint is that you won't have enough buttons to take advantage of this. Even then, there's a lot of real estate already used by the default keys.adept wrote:I don't see the problem, direct saves/loads don't have to be binded by default at all if you fear that this would lead zsnes users to not using all 100 states per game.Deathlike2 wrote:You do realize the number of buttons that would be needed for this?
Intelligent usage of the existing feature is the way to go, particular when there are 100 states, not just 10 states.
I'm not really for this because it introduces a host of other user-created errors that is not worth dealing with.
Continuing [url=http://slickproductions.org/forum/index.php?board=13.0]FF4[/url] Research...
My impression is that he's meaning two keys per slot.If you can think of a proper way to quickload/save that's actually quick and does the "one key per slot", feel free to share.
Eg F5 = save state 1, F6 = load state 1, F7 = save state 2, F8 = load state 2, ... F202 = save state 99 (joking here, of course. You'd only map a few.)
Sounds like a real pain to implement into the key mapping section. Would have to be some sort of scrolling listbox.
-
- ZSNES Shake Shake Prinny
- Posts: 5632
- Joined: Wed Jul 28, 2004 4:15 pm
- Location: PAL50, dood !
Hmm... we'll see. You better be patient though.
皆黙って俺について来い!!
Pantheon: Gideon Zhi | CaitSith2 | Nach | kode54
Code: Select all
<jmr> bsnes has the most accurate wiki page but it takes forever to load (or something)
Why not just pick the option that would make everyone happy
Interface Mode 1: 1-9 = Developers Buttons (Backgrounds on/off, etc)
Interface Mode 2: Shift + # (Write state), # (Read State)
Long story short, there are undoubtedly some people who like one way over the other. Not everyone needs the ability to turn off the foreground layer (something which is becoming less necessary for standard emulation, now that most of them work properly). Providing a switch ensures that both sides are happy, and it couldn't be that difficult to program.
Interface Mode 1: 1-9 = Developers Buttons (Backgrounds on/off, etc)
Interface Mode 2: Shift + # (Write state), # (Read State)
Long story short, there are undoubtedly some people who like one way over the other. Not everyone needs the ability to turn off the foreground layer (something which is becoming less necessary for standard emulation, now that most of them work properly). Providing a switch ensures that both sides are happy, and it couldn't be that difficult to program.
-
- ZSNES Shake Shake Prinny
- Posts: 5632
- Joined: Wed Jul 28, 2004 4:15 pm
- Location: PAL50, dood !
I really like when people don't read posts.Hal_Emmerich wrote:Interface Mode 2: Shift + # (Write state), # (Read State)
Really.
皆黙って俺について来い!!
Pantheon: Gideon Zhi | CaitSith2 | Nach | kode54
Code: Select all
<jmr> bsnes has the most accurate wiki page but it takes forever to load (or something)
-
- ZSNES Developer
- Posts: 6747
- Joined: Tue Dec 28, 2004 6:47 am
grinvader wrote:I really like when people don't read posts.Hal_Emmerich wrote:Interface Mode 2: Shift + # (Write state), # (Read State)
Really.
Ah the memories.I wrote:Intelligent usage of the existing feature is the way to go, particular when there are 100 states, not just 10 states.
Continuing [url=http://slickproductions.org/forum/index.php?board=13.0]FF4[/url] Research...