Bug 288368

Summary: KMail conflict dialog hard to read (different column widths)
Product: [Frameworks and Libraries] Akonadi Reporter: Christian Boltz <kde-bugs>
Component: libakonadiAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: amantia, pragma, sven.burmeister
Priority: NOR    
Version: 4.9   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Christian Boltz 2011-12-07 00:01:44 UTC 
Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

(initially reported as https://bugzilla.novell.com/show_bug.cgi?id=734595 )

The KMail 2 conflict dialog (when KMail detects that it has possibly stored 2 copies of a mail (or something like that) and asks which one to keep) is very hard to read.

The reason is that the columns showing the two mails have a different width (see screenshot at https://bugzilla.novell.com/attachment.cgi?id=465660 ), which means you can't directly visually compare both mails.

I'd propose the following changes:

1. easy to do and very useful: give both columns the same width

2. also easy: increase the default window size of the conflict dialog

3. harder: additionally implement highlighting of the differences - maybe you
can reuse kdiff3 for that?


Reproducible: Always

Steps to Reproduce:
.


Expected Results:  
.
Comment 1 András Manţia 2012-10-17 13:44:24 UTC 
*** Bug 289901 has been marked as a duplicate of this bug. ***
Comment 2 András Manţia 2012-10-17 13:46:10 UTC 
*** Bug 275232 has been marked as a duplicate of this bug. ***
Comment 3 András Manţia 2012-10-17 13:46:57 UTC 
This is actually an issue in Akonadi, not KMail.
Comment 4 Denis Kurz 2016-09-24 20:39:06 UTC 
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 21:50:21 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.