Quick settings

[cc]

I was thinking about the menu organisation, and I think that it's pretty good. The only problem I have is the number of menus I have to go though to get to some of the settings I use. I guess these particular settings are probably not the same ones everyone else wants... so, I thought it would be good to be able to copy the few settings I use regularly to a menu that could be accessed straight from the root menu - called "Quick Settings"? The size of the Quick Settings menu could probably be limited to some low number: 10?

What do people think? Sound useful? Dumb idea?

Note that it would only be individual settings (like "brightness"), not whole menus that could be accessed from this menu. Also the settings would still be available in the normal menus.

I have an idea of how I could implement this pretty cheaply: it would use the config file reading code, and the name of a setting followed by (say) a * would put the setting for it in the Quick Settings menu. I think it could work by just looking through the menus to find the menu_item_ex for that setting and putting a pointer to it into the Quick Settings menu. So, no extra data structures apart from the quick menu itself.

Other possibilities:

1) Allow users to configure it using the menus (not just the config file)  - maybe just a menu item at the end of each settings menu saying "Add to quick settings" (and afterwards a remove)

2) Putting the items at the end of the Settings (or root) menu instead of making  a new menu. OR allowing this option as well.

Any thoughts?

[Llorean]

Something like this has already been suggested, dozens of times.

Which settings do you change frequently? For example, with brightness, how many of the possible values do you use?

Why not use a few common setup config files?

[GodEater]

Why not use a few common setup config files?

Which is what I do - and it works just fine...

[cc]

Something like this has already been suggested, dozens of times.

Did anyone implement anything?

Which settings do you change frequently? For example, with brightness, how many of the possible values do you use?

Why not use a few common setup config files?

Yes, I use the config file route at the moment, but really I would prefer to be able to actaully adjust the brightness (edit: I mean so I can see it changing) . I also change the bookmark mode, the ff/rew speed settings, invert the screen, backlight timeout, the list gets kind of cluttered because you need one item for each value of each setting. And I would probably change more if it was easier.

[nls]

Did anyone implement anything?

No, because most devs think it's a bad idea.

[JdGordon]

Did anyone implement anything?

No, because most devs think it's a bad idea.

I did implement it _ages_ ago (dont ask for the patch, its long gone), and im one of the few (only?) devs that love the idea..

[nls]

ah, didn't know that, I'm not against this feature but I don't think I would use it that much, don't really need it.

[cc]

Thanks for the comments guys... of course I did it anyway  

Came in at just 50 lines of code.

In the end I went for putting the items straight into the root menu, although it would be trivial to make it add to a dedicated menu or the settings menu instead/as well. The cfg file entries look like this:

Code: [Select]

# put frequently used settings into root directory
brightness: +root
invert: +root
autocreate bookmarks: +root
autoload bookmarks: +root
scan min step: +root

[cc]

I lived with it a bit, found some wrinkles and added a feature to let you put the menu that contains a setting (using *root).

The patch in the tracker: http://www.rockbox.org/tracker/task/8011

Here's a screenshot:



And the /.rockbox/fixed.cfg file:

brightness: +root
invert: +root
autoload bookmarks: *root
foreground color: *root
scan min step: +root
party mode: +root

[bluebrother]

While it's called root menu in the source (due to historical reasons) we don't consider having a root menu -- if that menu (the main menu) would be a root menu it would behave slightly different. So there is no root menu. Just for completeness.

[cc]

Heh, I had just managed to stop being confused by the main menu in the code being the settings menu  

But I see your point, I have changed it to use +main and *main.

[bluebrother]

Thanks