Bug 93604 - Destination folder unclear when moving messages
Summary: Destination folder unclear when moving messages
Status: RESOLVED DUPLICATE of bug 108174
Alias: None
Product: kmail
Classification: Unmaintained
Component: GUI (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-19 22:39 UTC by Eggert Ehmke
Modified: 2007-09-14 12:17 UTC (History)
2 users (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 Eggert Ehmke 2004-11-19 22:39:09 UTC
Version:           Unbekannt (using KDE 3.3.1, Gentoo)
Compiler:          gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)
OS:                Linux (i686) release 2.6.9-gentoo-r4

I have defined several folders to maintain my incoming messages. When I select a message of the incoming folder (Posteingang) and move it to another folder, the destination folder is highlighted as long as the mouse button is pressed. When the mouse button is released, the options "move", "copy", "cancel" are displayed, but the destination folder is not highlighted anymore. So it is possible to move a message into a wrong folder.
Comment 1 Christian Boltz 2005-12-24 01:31:13 UTC
You mean something like I suggested in
http://bugs.kde.org/show_bug.cgi?id=108174 ?
Comment 2 Eggert Ehmke 2005-12-24 10:14:20 UTC
I guess so, yes. Until the moment you select "move" or "copy", the destination folder should be highlighted. A flashing is not neccessary.
Comment 3 Martijn Klingens 2005-12-24 10:58:28 UTC
A lot simpler approach would be to use KPopupMenu for the menu and put the name of the folder in the title, just like most (all?) context menus in e.g. the systray have.
Comment 4 Ismail Onur Filiz 2006-05-08 08:58:29 UTC
Marking duplicate. I know this bug is older, but the other one seems to have a more explicit description.

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