Bug 295955 - EntityMimeTypeFilterModel ignores newly added collection where only subcollections match filter
Summary: EntityMimeTypeFilterModel ignores newly added collection where only subcollec...
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.9
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-13 19:44 UTC by Daniel Vrátil
Modified: 2013-03-02 23:39 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 Daniel Vrátil 2012-03-13 19:44:16 UTC
When a new collection tree is added to Akonadi, where the root collection does not match current mime type filter, but it's children do match the filter, the collection tree is not displayed.

Let's have following tree of calendars/todo collections. When you create such tree and add it to Akonadi, it will not appear in the calendar list in KOrganizer. You have to restart KOrganizer to make them appear.

My Account  (Collection::collectionMimeType)
  |
  |------ My Calendar (KCal::Event::eventMimeType)
  |------ My Second Calendar (KCal::Event::eventMimeType)
  |------ My Tasklist (KCal::Todo::todoMimeType)


But if you create following tree (note the mimetypes in the root collection), the tree will appear in the calendar list immediately.

My Account  (Collection::collectionMimeType, KCal::Event::eventMimeType, KCal::Todo::todoMimeType)
  |
  |------ My Calendar (KCal::Event::eventMimeType)
  |------ My Second Calendar (KCal::Event::eventMimeType)
  |------ My Tasklist (KCal::Todo::todoMimeType)

Simply put, it looks like the filter does not check subtree of a newly added collection if the collection does not match the filter.
Comment 1 Daniel Vrátil 2013-03-02 23:39:43 UTC
Unable to reproduce anymore with recent version of Akonadi/kdepimlibs