byuu wrote:For power users / emu loader tools, I allow loading via command-line / file association to hide the menubar automatically.
For general users, when you enter fullscreen with a cart loaded, the menubar disappears. With no cart, you will have to show the menubar anyway in order to load a cart to play, then hide it again. So it should be shown. It even lets you know there's no cart loaded at the bottom right.
If one insists on loading games in fullscreen mode manually, then one extra key hit after is surely not a big deal.
Darn it, byuu, I jumped to conclusions after toggling without a rom loaded for the first time. Okay, so it only disappears when a rom is loaded. Here's the problem with that: if I don't know the fullscreen or menubar toggle, how do I get out? Once I use the fullscreen toggle from the menu with a rom loaded, the menu disappears. What do I do? And then if I manage to guess Esc to bring it back, I create a habit of doing it the long way because there's a good chance I still don't know a fullscreen toggle exists. Wouldn't it be better if only the toggle existed and I was told of its existence on first run?
a) I don't see why we can't have a menu entry as well as a hotkey. We don't remove 'Load Cartridge' because you can do that with a key binding. '[ ] Fullscreen' makes sense under "Video Mode".
The difference is that the action of toggling the mode or the menubars can make the menu disappear. No other actions do that. And the
only reason the menubar toggle exists at all is because fullscreen video settings can currently only be set via the fullscreen menu. That entire toggle could get wiped out if menu behavior was standardized.
I appreciate you arguing with me on this for so long, I'd have punched me by now. But here's what confused me about not getting that: you wanted the quickness of menu settings for video. Okay, understood... However, let's say the following actions were taken:
(a) the video section added both windowed and fullscreen settings
in addition to settings in the windowed menu.
(b)The fullscreen menu was removed
(c) The menubar/statusbar toggle was removed.
That would still give you fast changes for testing in windowed mode, and for everyone else it would vastly simplify fullscreen behavior. It's a win-win for everybody, right?
b) Should we document the ten other GUI hotkeys? That's what the GUI hotkey window is for. Yeah, there's a problem with people finding that. I don't have a good answer for that ... if we list the GUI keys first, people won't find the joypads. If we list the joypads, people won't find the GUI keys.
You understand exactly why I assume people won't find it beforehand. It's not that the input section is poorly designed, it is buried and there is simply no better place for it. You can get around this gracefully without touching that section, that's what I'm trying to help you accomplish.
I kind of take issue with that, but we're just splitting hairs here. You can put anything inside an SNES cart. I'm writing a Super NES emulator, not a game cartridge emulator (even if the latter is the end goal.) The cart special chips I add are icing on the cake, and aren't even focused on strict accuracy (due to time constraints, I'd like them all to be timing/bit perfect of course.)
I'm not trying to offend you, I'm just looking at it from the side of the user who has no idea that you consider savestates to be categorically more important than hardware required for many games. I know it makes your goal seem unattainable, but you
had to be thinking of the games before you did this: without software, the hardware is meaningless. Imagine if Der Langrisser had used the DSP1 chip, your view would change overnight, wouldn't it? I don't like it any more than you do that the SNES library used more unique processing units than any other console in history, but it is what it is.
That's what I was going with. I want to list that I don't support SuperFX, SA-1, etc. I know someone who's never heard of the SNES won't know what the hell they are, but I think most people using bsnes would.
Fair enough, but even a fairly knowledgeable user would look at "Unsupported Hardware" and assume an all-inclusive list. You could in some way hint at or explain that it's not.