Comment # 3 on bug 1161460 from Ancor Gonzalez Sosa

(In reply to macias - from comment #2)
> > Actually this is so consistent with the rest of YaST that it even uses a shared 
> > dialog
> 
> The fact some piece of code is shared does not mean it is actually USED the
> same way. So I stand exactly where I wrote this report.
> 
> The question serves no purpose, there were no changes, so there is no loss
> when quitting the app and the app is non-consistent with the rest of Yast.
> 
> Issue: does app ask when no changes were made and user quits it:
> NO -- Fonts
> NO -- Date and Time
> NO -- Printer
> NO -- Keyboard Layout
> NO -- Hardware information
> NO -- Software repositories
> NO -- Add-On Products
> (I skipped the rest as it seems obvious too me)
> and
> YES -- Services manager
> 
> I say it is inconsistent behavior.

You found 6 examples in which YaST acts in one way.

Doing this search[1] I found many more examples of what you have pointed
(modules that quit without asking)... but I also found examples of modules that
act like Services Manager does:

- Services Manager
- Firewall
- Mail
- NIS Server

So I will open the discussion in YaST devel. We need to make it consistent at
several levels. Specially because it looks like the majority of YaST modules
has decided to use the shared dialog... but bypassing its behavior. The API
should do what the majority needs. Instead of that, we have a majority just
cheating the API.