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

Qt: Introduce simplified mode #7691

Open
wants to merge 1 commit into
base: master
from

Conversation

6 participants
@spycrab
Copy link
Contributor

spycrab commented Jan 9, 2019

Simplified Mode

Obviously highly WIP!

This PR introduces simplified mode
which aims to help new and inexperienced users
by hiding settings that may confuse them.

Simplified mode will be enabled by default.

Things hidden by simplifed mode

(and why they are hidden)

  • Menubar (not on macOS): Has many entries that are also accessible using the toolbar.
  • Config
    • Advanced tab
    • Interface/"Show debugging UI": Can't be used while simplified mode is enabled
  • Graphics Window
    • Hacks tab: Contains settings that are mostly confusing to users
    • Advanced tab

Open Questions

  • This needs to be enabled by default but should not be forced upon existing users. How can we ensure this?
  • What else needs to be disabled?
  • Graphics: Do we need a "Safe"/"Fast" slider for all settings?

@spycrab spycrab added WIP RFC labels Jan 9, 2019

@legoj15

This comment has been minimized.

Copy link

legoj15 commented Jan 9, 2019

I agree with what @irishmapping said, except for the part about disabling/hiding cheats. I feel like users expect to find cheats as an option for any emulator (even if they don't end up using that feature), and hiding that setting from users under a setting that toggles the simplistic UI could actually cause confusion; there is a game on Steam called Space Engineers, and the developers had a similar idea to add a simplified menu as an option and to make it the default. This menu hid a lot of features that were expected of the game, and users who happened to purchase the game after this update were very confused as to why they couldn't make a custom world or enable mods and it tanked their reviews. So IMO two features that shouldn't be hidden are cheats and netplay (the netplay menu might benefit from simplification though).

Sorry for the block of text, just my stance on that idea and want to prevent new user confusion. I might give more feedback if I feel it's warranted.

@jordan-woyak

This comment has been minimized.

Copy link
Contributor

jordan-woyak commented Jan 9, 2019

I don't think a simple mode should be the default. Ask the user on first run if they are simple.

@Zexaron

This comment has been minimized.

Copy link
Contributor

Zexaron commented Jan 9, 2019

I don't think a simple mode should be the default. Ask the user on first run if they are simple.

The statistics reporting and this could share the same dialog on first boot, to save 2 dialogs from appearing.

But if more things get added, then I'd rather have it multi-paged, like a wizard. That's not unusual for programs. There's probably more things that could be added there that I can think of but that's for another discussion.

@mbc07

This comment has been minimized.

Copy link
Contributor

mbc07 commented Jan 10, 2019

This PR introduces the simplified mode to Qt only, Android won't be affected at all, at least not by the (current) scope of this PR...

@mimimi085181

This comment has been minimized.

Copy link
Contributor

mimimi085181 commented Jan 10, 2019

"Do we need a "Safe"/"Fast" slider for all settings?"
I would say yes. If you switch between simple and advanced mode, it shouldn't apply settings from advanced mode that are not visible in simple mode, at least not without clear indication. If you do the sliders, you could add a custom setting, if the actual settings don't match the fast/balanced/safe/safe+ presets. With that, it would be a clear indication that Dolphin is not really using simple mode, without just resetting your settings by clicking on the simple mode button.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment