Bug 56446 - Moving, Copying or deleting large amounts of messages blocks the GUI
Summary: Moving, Copying or deleting large amounts of messages blocks the GUI
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmail
Classification: Applications
Component: GUI (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 58162 62274 132398 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-03-26 20:06 UTC by Martijn Klingens
Modified: 2012-08-19 01:04 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martijn Klingens 2003-03-26 20:06:50 UTC
Version:            (using KDE Devel)

When selecting more messages in performing actions like move, delete or copy on them it becomes _very_ noticeable that this is a blocking action and doesn't leave the GUI accessible.

Ideally the action might be performed in the background, but at least consider showing a progress dialog when moving more than, say, 30 mails or when moving takes more than, say, 2 seconds. The latter is about the longest a non-repainting GUI doesn't feel uncomfortable with people thinking of hanging and such.

(Although one could argue that a blocking GUI is a usability bug I filed it as a wish for now to avoid you guys getting swamped with tons of unresolved bug reports - I know the feeling all too well :)

Martijn
Comment 1 George Staikos 2004-03-23 03:41:30 UTC
*** Bug 62274 has been marked as a duplicate of this bug. ***
Comment 2 George Staikos 2004-03-23 03:42:38 UTC
*** Bug 58162 has been marked as a duplicate of this bug. ***
Comment 3 George Staikos 2004-03-23 03:46:05 UTC
I think a progress dialog would be sufficient
Comment 4 George Staikos 2005-03-01 22:57:48 UTC
Any objections to processing non-socket events?  or non-socket and non-user events?
Comment 5 Don Sanders 2005-03-17 05:48:21 UTC
> ------- Any objections to processing non-socket events?  or
> non-socket and non-user events?


Yes. In addition to socket and user events, processing timer events 
would also be a bad idea I think.

Maybe processing  painting events would be safe though.

That's my 2 cents,
Don.
Comment 6 Björn Ruberg 2009-12-29 21:49:07 UTC
*** Bug 132398 has been marked as a duplicate of this bug. ***
Comment 7 Myriam Schweingruber 2012-08-18 08:33:34 UTC
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.
Comment 8 Luigi Toscano 2012-08-19 01:04:22 UTC
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.