Bug 186922 - Quit does not mean close the program
Summary: Quit does not mean close the program
Status: RESOLVED DUPLICATE of bug 180466
Alias: None
Product: kmail
Classification: Unmaintained
Component: GUI (show other bugs)
Version: 1.11.1
Platform: Fedora RPMs Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-12 07:11 UTC by Juha Tuomala
Modified: 2009-03-19 00:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juha Tuomala 2009-03-12 07:11:28 UTC
Version:            (using KDE 4.2.1)
Installed from:    Fedora RPMs

If I have few messages open, somewhere - as my desktop has multiple virtual desktops and messages are spread around different tasks - and due problems with program, I choose:

  File --> Quit

the main window disappears.

If I try to start the program again, the main window comes back very quickly and the same problem still persists. 

That is because kmail process never ended since I did not  close all open windows first and then choose Quit from main window.

IMO this is not logical and must be very confusing for non IT users. Firefox is a good example that Quit really shuts down all open windows and processes.
Comment 1 Kevin Kofler 2009-03-12 09:06:24 UTC
Well, while the behavior you're suggesting sounds the most logical to me, I'm not sure everyone will want their mail composing windows closed just because they closed the main window. And especially "non IT users" might not expect closing the main window to automatically close everything - expecting that implies you already have a mental model of which window is the main one and which ones are subordinates.

Any KMail developer available for a comment?
Comment 2 Jaime Torres 2009-03-12 09:22:07 UTC
Also look at the kde-core mails for 
"[PATCH] new CloseWindow and CloseDocument KStandardGuiItems"

*** This bug has been marked as a duplicate of bug 180466 ***