Jonas Häggqvist schrieb:
Again, I don't see how this will be surprising to the user. The
alternative is that a random theme (the one that sorts first) is selected.
At least most of the settings will probably still be from the loaded theme.
and finally, there is nothing stopping you from loading two
theme .cfg's and have them work together.
Huh? At any rate, I don't see how it will be surprising that the most
recently loaded one of the two is selected?
I agree with with rasher (and domonoky). I don't think it will create
confusion. And I think it's a handy feature.
The distiction between changing settings and loading .cfg's is already
pretty obvious (we call it "Browse ... [settings]", and show a splash
which makes clear it's a .cfg, not a single settings). And we can make
it even more clearer by covering it in the manual.
Sure, if you treat it as the current theme, it will be wrong almost
anytime, but if you treat it as last loaded theme config, then it will
be correct.
I don't think preselecting the last loaded theme (or equalizer etc) will
really cause a lot of confusion. Particularly if the comes with a
obfuscated UI, he might wonder why that theme is selected, but then he
should come to the conclusion that this is because it was the last
loaded one.