Bug 436794

Summary: Cannot delete an entry from contact group editor
Product: [Applications] kaddressbook Reporter: Jonathan Marten <jjm>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: montel, tokoe
Priority: NOR    
Version: GIT   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Contact group editor screen shot

Description Jonathan Marten 2021-05-08 20:12:30 UTC
Created attachment 138254 [details]
Contact group editor screen shot

SUMMARY

See screen shot.  When editing a contact group, the red '-' buttons to delete an existing entry overlay the displayed email address.  If the window is dragged wider then they move to the right, but they still stay at least an inch inside the right side of the list.

Clicking on one of the buttons, regardless of where they are located, does not delete the entry from the group.  If it is an entry which is a reference to an existing contact, then a combo box is displayed (extending all the way to the right of the list) listing the contact's email addresses.  If it is an entry which is not an existing contact, then the email address changes to editable.  There appears to be no way to delete an entry using the GUI, the only solution is akonadiclient.
Comment 1 Jonathan Marten 2022-07-08 07:23:33 UTC
Still a problem with current PIM.

Suspect this is a Qt bug involving the use of QIcon::paint() with an alignment flag in ContactGroupEditorDelegate::paint().
See https://bugreports.qt.io/browse/QTBUG-104847, it may be possible to work around if there is no fix.
Comment 2 Jonathan Marten 2022-07-08 08:45:07 UTC
Note that clicking at the extreme right of the entry, where the button would be expected to be, does correctly delete the entry.  So the problem is a visual anomaly only.
Comment 3 Laurent Montel 2022-07-08 08:55:22 UTC
Already fixed in master 75525b4dbbb473a0f6ee0cf5ab1ac6096522c15b
Comment 4 Jonathan Marten 2022-07-08 10:03:04 UTC
Thanks Laurent, that is almost exactly the fix that I would have suggested.
Leaving the Qt bug open for information.