http://bugzilla.novell.com/show_bug.cgi?id=886906 --- Comment #2 from Antoine Saroufim --- Perhaps I didn't convey my message properly. It would be fantastic to integrate YaST into the control centre of several popular environments. However, that's not what I had in mind when I filed this bug. What I'm suggesting is something similar to what KDE and GNOME have. After you click on "YaST" from GNOME's Control Center, you get a popup with YaST's main window. That's all right. I'm not suggesting we change that. What I'm proposing is all of YaST's modules should be displayed within YaST's main window so the user would have one YaST window (as well as GNOME control center's window). When you click on "Privacy" in GNOME's control center, the main window changes into the privacy module's window. On YaST, if you click on "software management", you would get a "YaST - Software Management" window as well as YaST's main window. This is the behaviour that I'm suggesting we should change. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=886906 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(locilka@suse.com) | --- Comment #4 from Lukas Ocilka --- This is definitely the expected behavior. Control center can open more different applications (here: Yast modules) at the same time. Explanation: Similarly to an undefined desktop environment, you can always open several windows at the same time with different applications. Use can also open several control centers, so why not Yast modules? But we could rephrase this a bit... Use case: I, as a user, always want to open a single instance of an application when launching it from control center, in order to prevent from changing the same configuration from two or more instances of the same tool. Side note: Firefox let's you open the same page three times. Thunderbird let's you connect to the same IMAP server from three different instances. You can also run several xterms and the very same Yast module in it.

From my POV, this should be done per module by locks: If there is a potential of breaking configuration by modifying it using several instances of the same Yast module twice, Yast should tell the user that a.) The same Yast module is already running and tell them to close it b.) The same Yast module is already running and whether they really want to continue (might make sense if the subsequent run is, e.g., for read-only access)

All in all, this is a feature request and if you really want it, I suggest using https://features.opensuse.org/ for creating new feature request. -- You are receiving this mail because: You are on the CC list for the bug.