Bug 302159 - Cursor hot-spot wrongly positioned when dragging emails around.
Summary: Cursor hot-spot wrongly positioned when dragging emails around.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-18 23:57 UTC by Jim Adamthwaite
Modified: 2017-01-07 22:23 UTC (History)
0 users

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 Jim Adamthwaite 2012-06-18 23:57:34 UTC
When clicking and dragging old emails from message list to trash folder, the cursor hot-spot is placed in the MIDDLE of the arrow-head.  The same is true when the ensuing dialog prompts for "Move here, Copy here or Cancel" options.  One has to be very careful to avoid mistakenly selecting a neighboring field.

This might account for other bug reports which state that when moving an email, the original is kept.  This is probably caused by "Copy here" being mistakenly selected, due to the hot-spot offset error, as mentioned above.

Reproducible: Always

Steps to Reproduce:
1. Click on an email subject heading line.
2. Drag it to the Trash (for example) folder and HOVER without releasing.
3. Note how the box outline changes as you move the cursor gently up and down.
4. From this one can deduce the cursor's hotspot position.
5. Release the mouse button to drop the email.
6. Note the same occurs during the ensuing "Move, Copy, Cancel" pop-up dialog.
Actual Results:  
Wong widgets or destinations can be selected.

Expected Results:  
World peace, immortality, endless pleasure.

I am impressed with the job you have done.  It's good and getting better.
Comment 1 Denis Kurz 2016-09-24 18:24:03 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:23:23 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.