After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 272277 - Double click on 'Contacts' in select contacts popup, Adds/Removes user from selected list
Double click on 'Contacts' in select contacts popup, Adds/Removes user from s...
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Contacts
2.2.x (obsolete)
Other All
: Normal normal
: Future
Assigned To: Sarfraaz Ahmed
Evolution QA team
Depends on: 209605 248127
Blocks:
 
 
Reported: 2005-02-07 11:32 UTC by Poornima
Modified: 2013-09-13 00:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Poornima 2005-02-07 11:32:34 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. Right click on a folder in 'Exchange' component, select 'Permissions'.
2. In 'Select Contacts addressbook, select a contact click on 'Add User'
Adds that user. If I double click on that id which is added, it will remove
it. 
Actual Results:


Expected Results:


How often does this happen? 
Always

Additional Information:
Comment 1 André Klapper 2005-02-09 17:43:48 UTC 
at the moment it's the only way to remove a person, see bug 209605 / bug
248127. adding dependency.
Comment 2 André Klapper 2005-10-08 03:27:06 UTC 
in order to destroy the UI component (as discussed with jpr, dobey, and nags),
changing component and reassigning. adding usability keyword.

i wouldn't consider this as a bug.
Comment 3 Srinivasa Ragavan 2005-10-18 05:12:04 UTC 
exchange stuff.
Comment 4 Sushma Rai 2005-10-19 10:33:22 UTC 
on dobule click (row-activated signal), we either add an entry to To: filed
or remove an entry.
Though there are add and remove buttons now, adding and removing by 
double-click is easier to use.
So I feel there is no harm in having it and we should not remove this functionality.

If any one is having a different opinion, please re-open the bug.