Version: (using Devel) Installed from: Compiled sources Is there a reason why settings are not applied automatically and I always have to hit apply button? You could also remove the "unsaved changes" dialog.
What do you mean automatically? Changes should be applied only if user wishes to -- how can you tell for sure user does not want to cancel changes?
If user clicks on a checkbox then I'm pretty sure that he wants to change that. Why would he want to cancel changes if he wanted them 2 seconds before? If he clicked that checkbox by mistake, he can click on it again to cancel them.
Vedran, it is absurd and contradiction of well established UI design. Just an example: I would like to see how A would look like with a1, a3, a7, a8 feature turned on, a2, a4, a9 turned off. So I have to change the state of 7 options to see the effect. And in general those are not said are checkboxes -- those could be fine-grained values. If you are not still convinced, go to Color module, change the whole set by hand, and then change each color you changed before (still manually) to exact same value it had before. Easy task right? That's why we have apply button and that's why we have undo and cancel button. To safely test changes. First of all this report is nothing like bug at all, but a wish. And what's more it is INVALID.
No, this what you are saying is not possible. In color module I changed a few things, then clicked "apply" to actually *see* the changes I've made and there's no way I can undo or cancel my changes if I'm not happy with them. The "reset" button is grayed out, so I have to do it manually. But yes, I would like to be able to do it. You can file another bug report or wish for "Undo last applied changes" button.
> No, this what you are saying is not possible. No, of course it _is_ possible. I am just saying it is bad UI. Ok, simpler example, you use theme black on white, you would like to change it white on black. Now, with change-and-apply UI you have to make extra steps black/white -> green/white -> green/black -> white/black because it is impossible to have such way black/white -> white/white (game over) So, change-and-apply is efficient in many cases (more than change-then-apply) but it is not safe in _all_ cases. Thus change-then-apply is must-have UI, because it works _always_. And any desktop env. cannot have two non-consistent UIs, I hope you will agree with that.
KDE does not do implicit saving, therefore this wish will not be implemented.