Bug 203876 - Disabled CollectionView when shown with CollectionRequester
Summary: Disabled CollectionView when shown with CollectionRequester
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: libakonadi (show other bugs)
Version: 4.3
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-14 20:20 UTC by Sascha Peilicke
Modified: 2017-01-07 22:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
testcase (code) (905 bytes, text/x-c++src)
2009-08-14 20:22 UTC, Sascha Peilicke 		Details
testcase (CMakeLists.txt) (310 bytes, text/x-cmake)
2009-08-14 20:23 UTC, Sascha Peilicke 		Details
screenshot (24.43 KB, image/png)
2009-08-14 20:24 UTC, Sascha Peilicke 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sascha Peilicke 2009-08-14 20:20:43 UTC 
Version:            (using Devel)
Compiler:          gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) Target: x86_64-suse-linux
OS:                Linux
Installed from:    Compiled sources

When a CollectionRequester object is created and initially disabled (via setEnabled(false)), the CollectionView inside the corresponding CollectionView remains disabled even after setEnabled(true). It seems that the changeEvent is not correctly propagated but so far I failed to find out why. The attached code can be used to reproduce the issue as seen on the (also) attached screenshot.
Comment 1 Sascha Peilicke 2009-08-14 20:22:32 UTC 
Created attachment 36155 [details]
testcase (code)
Comment 2 Sascha Peilicke 2009-08-14 20:23:47 UTC 
Created attachment 36156 [details]
testcase (CMakeLists.txt)
Comment 3 Sascha Peilicke 2009-08-14 20:24:09 UTC 
Created attachment 36157 [details]
screenshot
Comment 4 Sascha Peilicke 2009-08-14 20:28:06 UTC 
CC'ed Ingo Klöcker.

I actually meant:
"the CollectionView inside the corresponding CollectionDialog ..."

It is also noteworthy that this doesn't happen when Akonadi::CollectionView is used standalone or when used only through a Akonadi::CollectionDialog.
Comment 5 Ingo Klöcker 2009-08-17 23:42:47 UTC 
I think it's better to ask on the kde-pim mailing list. Bugzilla is for users reporting defects, but not for developers reporting problems with the libraries.
Comment 6 Frederick Alexander Thomssen 2009-08-21 14:12:05 UTC 
Actually, I (a user) reported it directly to Sascha instead of opening a bug report here. So it's not quite misplaced...
Comment 7 Sascha Peilicke 2009-11-03 12:15:28 UTC 
it's confirmed by a testcase and user reports
Comment 8 Tobias Koenig 2010-06-20 15:51:29 UTC 
Hej,

this problem is caused by the Akonadi::Control::widgetNeedsAkonadi() call in EntityTreeView. The logic in widgetNeedsAkonadi() seems not handle enable/disable states correctly.
Volker, can you have a look at it, please?

Ciao,
Tobias
Comment 9 Denis Kurz 2016-09-24 20:39:50 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 10 Denis Kurz 2017-01-07 22:21:20 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.