https://bugs.kde.org/show_bug.cgi?id=521620
Oskar <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Oskar <[email protected]> --- Kclock is only designed to have one instance. If we allowed multiple instances it would mess up the kclockd backend and probably the tray icons. Allowing only a single instance allows us to have a more focused user experience. Furthermore, adding another stopwatch to the UI would keep the cohesiveness of the application without expanding its complexity. The question is: How big is the desire to add support for more stopwatches? And also, why don't other timer apps allow for multiple stopwatches? -- You are receiving this mail because: You are watching all bug changes.
