Version: unknown (using KDE 3.1.9) Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB-athlon I have alot of (and for the most part unorganized) bookmarks. The problem I am having now is that because i have so many bookmarks, when I display my bookmarks, it takes over the whole screen (see attached screenshot). Also, since it does also go over the bookmark menu item, I will many times have it pass a click on one of the links unless I hold down the button until the listing comes up and then releasing on the bookmark I wanted. I think an idea would be to have it display a "More >>" link at the bottom of a full pull page (and not have it go over the bookmark menu item at any time), or implemeent something simliar to IE (boo, hiss) and a down arrow that scroll down (I'm not a huge fan of this as to get down to the bottom takes forever). Lastly, maybe add a scroll bar to the side of the listing when it does exceed one row.
Created attachment 2300 [details] Alot of bookmarks
I just noticed that the quick browser menu item you can add to the kmenu has this setup like I was requesting. Maybe it would be possible to reuse that code in this situtation? (I attached another screenshot showing the quick browser)
Created attachment 2302 [details] More option in quick browser
please search for previous bugs in here on the topic - qt/kde already has scrolling popup menus. Alex
I was unable to find any related bugs when I had initially written the bug report. I am still unable to by using the topic you provided to search by. Can you give me the bug(s) report numbers so I can look at them.
Actually, this bug is far from resolved. Just look at the bugs bug 56897 + bug 58733 + bug 59401 + bug 128410 + bug 139665 for some examples, then at your own Konqui (in case you have more than 50 bookmarks) or see this screenshot: http://bugs.kde.org/attachment.cgi?id=18587&action=view and you'll notice it is still the same.
Reopening bug because it is not fixed (but will close it again as duplicate since it is reported elsewhere too :-) )
*** This bug has been marked as a duplicate of 137373 ***