Bug 314474 - Cannot edit multiple entries in Kaddressbook simultaneously
Summary: Cannot edit multiple entries in Kaddressbook simultaneously
Status: REPORTED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: 4.9
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-05 20:13 UTC by K. A. Sayeed
Modified: 2021-03-09 02:33 UTC (History)
4 users (show)

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 K. A. Sayeed 2013-02-05 20:13:35 UTC
1. In KDE version 4.3.2, it was possible to open and edit multiple contact entries in Kaddressbook simultaneously. This is not possible in version 4.9. As a matter of fact, when on contact entry is opened for editing, Kaddressbook becomes gray and it is no longer possible to have access to any other contact entry. Will it be possible to open and edit multiple contact entries in version 4.10?

2. This feature is absolutely necessary for the following reasons:

2.1. Some times it becomes necessary to view more than one contact entry (for example, in order to compare them).

2.2. Some times it becomes necessary to view and copy information from one contact entry for use in creating or editing another contact entry.

2.3. The inability to open and edit multiple contact entries simultaneously makes the use of Kaddressbook much more difficult and much less efficient.

3. One wonders why versions of Kaddressbook after version 4.3.2 have regressed in this matter.
Comment 1 K. A. Sayeed 2013-02-05 20:14:35 UTC
1. This bug is always reproducible.
Comment 2 Allen Winter 2013-02-08 18:41:27 UTC
I believe I fixed this already  in 4.11
I can double-click on multiple contacts in the list and have an editor for each one simultaneously.

Is that what you want?
If so, I can look at backporting into 4.10 for the 4.10.1 release.
Comment 3 Justin Zobel 2021-03-09 02:33:58 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.