Bug 186433

Summary: Collect modal messages per application in a single dialog
Product: [Unmaintained] kdelibs Reporter: Nicos Gollan <gtdev>
Component: kdeuiAssignee: kdelibs bugs <kdelibs-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Nicos Gollan 2009-03-07 10:54:32 UTC
Version:           4.1.2 (using KDE 4.2.1)
OS:                Linux
Installed from:    Unlisted Binary Package

I would like to propose an improvement in the handling of multiple modal messages being generated by a single application. Those Messages/events should be queued and presented to the user in a single modal dialog connected to the application requiring attention.

As an example, take certificate warnings in KMail/Kontact. I am currently accessing four IMAP mailboxes, but none of those is using an SSL certificate issued by a recognized CA, so I get (at least) one warning per mailbox. Those warnings are presented in separate dialogs, placed randomly around the center of the screen/parent window. Sometimes, even the order of those dialogs will be screwed up, so I can't go through the messages until I find the current "top" one. Additionally, accepting a certificate will open a new dialog asking if the certificate should be accepted temporarily or permanently, which will again be placed with a slight offset, making for a neat little game of hunt and seek.

A potentially better system would collect all those dialogs in a queue representing the order in which the dialogs have to be answered, and presenting them to the user in a single dialog, along with a counter how many requests are pending, perhaps an indicator of importance, etc.
Comment 1 Christoph Cullmann 2024-09-14 16:17:47 UTC
Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann