Version: (using Devel) Compiler: gcc 4.3.2 OS: Linux Installed from: Compiled sources - Launch Kaddressbook (=KAB) - Go to Settings menu/Toolbars/Navigator Note: the Main Toolbar should be checked by default. It it is not please do check it. - 9 buttons appear on the top right hand side of KAB (To-do List...) But because the search field is so wide you have to click on the '>>' button to see them all. I do not think that such a long search field is needed and if reduce that could leave enough space for all the buttons to be displayed. If you think that the search field size should not be modified then there is also the possibility of displaying the 'Navigator' toolbar underneath the 'Main' toolbar. This could be an improvement in KAB but also in other programmes like the 'popup Notes' or the 'Time Tracker' display Trunk, Svn Rev 1022237
This is functionality from Kontact, not KAddressBook. Please try to use KAddressBook standalone to find KAddressBook specific problems. Ciao, Tobias
Tobias, I was asked to test KAB within Kontact. But, in the future I'll select Kontact in the 'Product' combo box when the bug is not KAB specific. Additionnal comments: If you move the Navigator toolbar so that all the 10 buttons are visible next to the Main toolbar then the Main toolbar is the one that gets reduced. You have to expand it again to see its contents (New Contact button,Sync Contacts, Search field). So it seems that it is impossible to put the two toolbars next to each other unless removing a few buttons when using a 1400x1050 pixels screen. It seems that the best solution would be that the Navigator toolbar appears underneath the Main toolbar by default. Trunk, Svn Rev 1033074
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
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.