Bug 226383 - No way to make all contacts visible
Summary: No way to make all contacts visible
Status: RESOLVED FIXED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 226385 229079 231620 233095 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-11 21:12 UTC by Anders Lund
Modified: 2010-05-08 16:30 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2010-02-11 21:12:04 UTC 
Version:           4.4 (using 4.4.00 (KDE 4.4.0), Chakra)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.32-ARCH

The new akonadi-based addressbook is lacking the means for making all resources active, so that all contacts can be searched/viewed.

May I suggest makeing the resource list contain checkboxes, like in korganizer? In addition, the contact view should provide information about which resource a contact belongs to.
Comment 1 Anders Lund 2010-02-11 21:17:25 UTC 
*** Bug 226385 has been marked as a duplicate of this bug. ***
Comment 2 Tobias Koenig 2010-03-02 10:55:05 UTC 
*** Bug 229079 has been marked as a duplicate of this bug. ***
Comment 3 Tobias Koenig 2010-03-22 09:18:42 UTC 
*** Bug 231620 has been marked as a duplicate of this bug. ***
Comment 4 Tobias Koenig 2010-04-03 08:22:37 UTC 
*** Bug 233095 has been marked as a duplicate of this bug. ***
Comment 5 Tobias Koenig 2010-05-08 16:04:28 UTC 
SVN commit 1124271 by tokoe:

Allow the user to select which address book content shall be
included in the middle pane via checkboxes. Now it is possible
to search over all contacts again

BUG: 226383


 M  +1 -1      CMakeLists.txt  
 M  +53 -24    mainwidget.cpp  
 M  +2 -0      mainwidget.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1124271
Comment 6 Dj YB 2010-05-08 16:30:55 UTC 
thanks,
what version is this fix going to be included in?