Bug 164745

Summary: Please remove the throbber from the menu bar
Product: [Applications] konqueror Reporter: Malte S. Stretz <mss>
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bluedzins, clintonthegeek, finex
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Malte S. Stretz 2008-06-23 13:03:40 UTC
Version:           4.00.83 (KDE 4.0.83 (KDE 4.1 Beta2) (using 4.00.83 (KDE 4.0.83 (KDE 4.1 Beta2), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-19-generic

Wow, I can't believe that a wish like this exists since KDE 2 (bug 17062 which I just marked a duplicate of 61322 which has more discussion).  But moving the throbber to the menu bar was actually a bad decision for KDE4:

(a) In the menu bar I was at least able to remove it, can't edit the menu bar (at least I didn't find a way to do so).

(b) I want/need to save as much vertical screen estate as possible on my screen (think Eee PC for a more extreme example).  So I set my menu font to 7pt (big enough for me anyway).  But now I've got quite a bug unused space between menu bar and toolbar because the throbber will keep the menu bar at the former height.

Why didn't you move it to the status bar or chose a suggestion from bug 61322?  Anything is better than the menu bar.
Comment 1 FiNeX 2008-06-23 14:25:16 UTC
I'm sure to have read about this on a bug reported some days (or weeks) ago but I cannot find it.

@Maciej: you're my personal DB, do you remember something about it? :-) :-)
Comment 2 Maciej Pilichowski 2008-06-23 17:16:27 UTC
Unfortunately no, I think I saw the bug Malte mentioned and that was it.

Btw. currently this is HIG violation. Toolbar is the best place to put the gear icon (and additionaly in tab bar).
Comment 3 Christophe Marin 2008-06-23 23:27:33 UTC
I'm surprise Maciej doesn't remember since he wrote this wish :-)



*** This bug has been marked as a duplicate of 163519 ***