| Summary: | Collection configuration: Too many remove-buttons after removing one collection | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Michael G. Hansen <mike> |
| Component: | Setup-Database | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version First Reported In: | 1.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.1.0 | |
| Sentry Crash Report: | |||
| Attachments: | Extra remove buttons in the collection manager after removing one collection. | ||
|
Description
Michael G. Hansen
2009-12-23 20:46:54 UTC
Created attachment 39293 [details]
Extra remove buttons in the collection manager after removing one collection.
This is another bug in KWidgetItemDelegate, which is pretty much broken for tree views. For 182753 I found a workaround, this time I did not (emitting dataChanged() does not help, we are already emitting layoutChanged()). This must be fixed in kdelibs. *** This bug has been marked as a duplicate of bug 187820 *** Fixed with #187820 |