would this feature be at all useful?

[JdGordon]

trying to toss up if a idea I had last night would be at all useful (and actually used)

the basic idea is to allow skins to have user settings which arnt part of the config.cfg file, and are shared by all skins (maybe a flaw, but no way around it)

it means that a skin could do something like %?Ss|my setting|<option 1|option 2|option 3|etc> allowing the user to choose which of those options they actually want.
The user side of it would be a plain text file sitting in .rockbox/wps probably named settings.txt or something which would then have a line like "my setting: 3" (it would always be numbers 1->whatever... so the themer would have to let the user know what each value means).

If people think this is useful then I have no problem doing the code (maybe 15min work ) but if its not something which would likely be used then I wont bother...

[Llorean]

I really don't get what you're describing here. Or maybe I do. I'm not sure.

Do you mean themes having custom "setting" names. For example, all of Bob's themes could have a setting named "Volume Display Format" which has 3 values, each representing one of three different ways he likes to draw volume bars, so that all of Bob's settings can know the user's preference for volume display, outside of a core setting for such?

[JdGordon]

yes.

To be honest, the only reason I can think of for using this is the classic_statusbar.sbs so it can have the icon and text battery and volume indicators in one sbs file... but maybe others do have a good idea for it.

[Llorean]

I think that it's one of those ideas that sounds useful, but doesn't have too many real uses.

Maybe we should see if people can think of good uses for it first.

[Rizzly]

To me it just looks like a waste of time to code. If the creator of a skin wants the skin to have different things to display, the creator can just make 3 versions of the skin, no?

[kugel.]

Doesn't sound really useful to me.