[systemsettings] [Bug 421929] Launching independent KCMs now acts over existing systemsettings instance
https://bugs.kde.org/show_bug.cgi?id=421929 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from Nate Graham --- Yeah. See bug 402790. We got persistent complaints about the old behavior, so we changed it to this. Also, for me when you switch to another KCM, if the already-open KCM has unsaved changes, it prompts me to save them. If you're seeing otherwise, it's probably a bug in that KCM itself rather than in the whole mechanism. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421929] Launching independent KCMs now acts over existing systemsettings instance
https://bugs.kde.org/show_bug.cgi?id=421929 --- Comment #2 from bluescreenaven...@gmail.com --- I guess, I am not sure if the new Windows 10 like behavior is best though, where opening a KCM from krunner or a context menu of a plasmoid, tries to open a full instance of System Settings, which then just takes over your existing instance, instead of opening a new window. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421929] Launching independent KCMs now acts over existing systemsettings instance
https://bugs.kde.org/show_bug.cgi?id=421929 Marco Martin changed: What|Removed |Added CC||notm...@gmail.com --- Comment #1 from Marco Martin --- this is done by purpose. is not possible to have 2 kcms instances open and everything must be done in order to avoid to ever have such a situation. -- You are receiving this mail because: You are watching all bug changes.
