Version: (using KDE KDE 3.3.1) Installed from: SuSE RPMs OS: Linux When starting kaddressbook the positioning of the view and/or address is confusing. I use the "rolodex" view which needs more space than available on the screen. So i can/must scroll horizontally to see all addresses. Sometimes one of the alphabeticaly first addresses are focused and the view is positioned correct (f.e. first address, the first address is shown in the left-adjusted view). The other time the (or one of the first) adresses are focused (let's say selected) but the view is positioned centered. So you can't see the focused address without scrolling. Another startup of kaddressbook the view is centered and one of the aphabetically "middle-sorted" address is focused (say the view is positioned correct). Couldn't find out on which scheme this happens. This happens on table view to. Wouldn't it be better to always focus on the first DISPLAYED address. So f.e sorting is honored? An alternative (which i DON'T prefer) is to remember the last focused (selected) address. BTW: I'm using two addressbooks. The focused address comes from one or the other addressbook. No scheme identifiable.
*** Bug 102920 has been marked as a duplicate of this bug. ***
Seems to work in 3.5.0
Nope, I still see a variation of what I described in bug 102920: The first address in my std.vcf (aka the first loaded contact) has the focus, although it is only the dotted version now. The effect: On startup KAddressbook jumps to a contact roughly in the middle of my address book which is still a bit odd.
*** Bug 127566 has been marked as a duplicate of this bug. ***
Rudolf, can you provide any reproducable step by step testcases? Or any hints on how you use KAddressBook when you see this bug?
Hello, it is very funny: When using the kaddressbook plugin inside of kontact, the view is positioned in the way, that the alphabetical first address is shown as the first address on screen. But when using kaddressbook _standalone_, than the display starts with a random contact. On startup you can see that the display flashes and than is so positioned, that a random address is the first on screen. The sort order is correct. Currently the display starts with a contact beginning with "H". When i scroll to left (with the horizontal scroll bar), i can see the (sorted) addresses before "H". I don't know how i could give you a good testcase. I have some addressbooks, open kaddressbook standalone and the bug appears. I unfortunately cannot confirm to Malte that the first contact in the vcf is used. I is not the first and not the last. I changes time by time, don't know when. It isn't the last contact used and not the last contact edited. It's randomly. I try to send you a screenshot. But it's some work to mask the contacts.
Created attachment 18325 [details] This shows the kaddressbook plugin view after startup This screenshot shows the view of the kaddressbook plugin in kontact after startup (switching initially to the plugin after kontact was startup)
Created attachment 18326 [details] This shows the kaddressbook standalone view after startup This screenshot shows the view immediately after kaddressbook is startup. Here you can see, that the first shown contact starts with "H" and not with "A" as it should.
Created attachment 18327 [details] another standalone startup, first backend element selected Hmmm... here its still always the first contact from the data base. Now that I switched to a directory backend, it is the contact with the lowest (alphabetical) id (see attached screenshot). When the app starts up, the item is first actually selected (details in right pane) and then deselected again, only leaving the focus rectangle.
The behaviour I described in #127566 still exists in 3.5.3 (Kontact 3.5.5).
Now when i start kaddressbook standalone, every time i get another contact displayed as "first on screen". The main differences between Maltes and mine scenario is: - i use vcf-files - displaying starts with "wrong" contact, but the contact currently isn't focused (no rectangle around). - i use "rolodex" view I use multiple active addressbooks stored in vcf-files. Some are local, some reside on a smb share. And - some contacts are "hidden" because of a filter on categories. Malte: what happens if you view your contacts inside kaddressbooks kontact plugin?
Inside Kontact I've got the same behaviour: Till is selected after I started it. Also in Rolodex though I don't see the focus rectangle after the contact gets unselected (try list view I guess you'll have it there, too). As you've got several backends, is it possible that it always selects one of the first contacts in any of this (with randomly changing vcf file)?
When i switch to table view i can reproduce Maltes report: in my case always the first contact of one of the vcf-files is selected. Regardless of plugin or standalone. And it is always the same vcf-file concerned! But in rolodex view i never get this in the plugin and completely random when standalone. I searched all backends and the contacts "first shown" are sometimes in the middle of a file, at the end or start (but till now it never happened that it was the first or last). And it isn't always a contact from the same backend.
Crazy, crazy, crazy! My above written comments are true for the newest KDE 3.5.5 version of SuSE RPMs, installed on a SuSE 9.3. But only for this! I can confirm ALL the comments of Malte when using the newest KDE 3.5.5 version of SuSE RPMs on a SuSE 10.1!!!!!!! It seems, there are differences. Mostly in the rolodex view. In my 10.1 box at home i get the identical behavor standalone as well in the plugin :-(
Hehe. Weird. Just for the records: I tried it on Gentoo and since this bug is open for quite some time with different versions of gcc and different libs etc.
SVN commit 633292 by tokoe: Always select the first entry of the view on startup. In KDE 4 we'll have a much better view handling! BUG:94253 M +10 -1 kabcore.cpp --- branches/KDE/3.5/kdepim/kaddressbook/kabcore.cpp #633291:633292 @@ -965,15 +965,24 @@ void KABCore::addressBookChanged() { + const QStringList selectedUids = mViewManager->selectedUids(); + mAddressBookChangedTimer->stop(); if ( mJumpButtonBar ) mJumpButtonBar->updateButtons(); mSearchManager->reload(); + mViewManager->setSelected( QString::null, false ); - setContactSelected( QString::null ); + QString uid = QString::null; + if ( !selectedUids.isEmpty() ) + uid = selectedUids.first(); + + mViewManager->setSelected( uid, true ); + setContactSelected( uid ); + updateCategories(); }
Sorry, but your patch doesn't work. It jumps to an "early" entry in the addressbook, but not the first one "alphabetically".
Created attachment 19682 [details] After patching first entry is not selected
The development of the old KAddressBook will be discontinued for KDE 4.4. Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.