https://bugs.kde.org/show_bug.cgi?id=503767
Alexander Potashev <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REPORTED Resolution|WORKSFORME |--- --- Comment #4 from Alexander Potashev <[email protected]> --- > Would it be enough to discard or save your changes to the shortcut (for > example) before making other settings changes? Ideally, this shouldn't be required because it interrupts my workflow. One of the settings changes may be more urgent than another, for example I can imagine doing something urgently in a new activity and not wanting to spend time on finalizing shortcut settings changes that are non-urgent. There's also the aspect of human context switching which is expensive: If Plasma asks me about shortcuts, * I need to stop thinking about activities and start thinking about shortcuts * Once I'm done reviewing the shortcuts, I need to start thinking about activities and recall what I wanted to do with activities. There was probably a chain (rabbit hole) of things I was doing as "dependencies" of the original goal, creating an activity being one of them. Having to discard/save shortcuts increases the depth of the rabbit hole by one. Of course I can strictly sequence every configuration change, but that requires additional effort / brainpower / time, and may be inappropriate in situations where there's urgency. Filed https://bugs.kde.org/show_bug.cgi?id=508972 which would fix the current issue. Although the current issue can be fixed without https://bugs.kde.org/show_bug.cgi?id=508972 by providing a separate UI to an create activity that doesn't involve running System Settings. -- You are receiving this mail because: You are watching all bug changes.
