Bug 169250 - Amarok2 menu hiding with Ctrl+M
Summary: Amarok2 menu hiding with Ctrl+M
Status: RESOLVED INTENTIONAL
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.0-SVN
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-16 18:43 UTC by Fri13
Modified: 2008-09-14 16:32 UTC (History)
1 user (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 Fri13 2008-08-16 18:43:12 UTC
Version:           2.0-SVN (using 4.1.00 (KDE 4.1.0), Mandriva Linux release 2009.0 (Cooker) for i586)
Compiler:          gcc
OS:                Linux (i686) release 2.6.26.2-desktop586-1mnb

Add menu hiding support to Amarok2, so user can hide menu with Ctrl+M.
Keep the shortcut disabled/emtpy by default but allow users who needs that functionality, to add key combination for the action to get it used.

The menu bar takes space and it is not needed in daily use, it makes the Amarok2 look more distracting because play control buttons are not top etc.
It is bad usability to not allow users to configure application as they want, the default should be simple and clean but configuration possibilities is needed.
Comment 1 Kevin Funk 2008-08-16 18:49:06 UTC
Yup, the "hide menu" option was removed due to a large number of users inadvertently hiding it and not knowing how to restore it. We have had several of these users a day on the IRC channel. 
- Nikolaj

Maybe ask the kdelibs team to improve the hidden menu handling. Because there's really no hint to get the menu back if the user accidentally hides it.
Comment 2 Fri13 2008-08-17 12:12:54 UTC
There is no need for hint when it is only a shortcut what is not enabled by deufalt (so novice user, who does not know about it, cant hide menu!) and it is not on menu-what would allow accidental menu hiding.

The problem is that is not KDE wide action, because it should be working in way; User hides menu first time with menu or shortcut > information box comes up what needs user to press "OK" and mark it does not come anymore, to confirm to knowing what he has just done. After that, it would not get showed on any application, unless user did not mark it. 

Some developers has got same attitude than Gnome developers, if it is possible there is 5% of users who gets it confused, it needs to be removed. It does not matter if 50% or 95% wants that feature to be added. They solve the problem with easiest possible way, just removing it, without actually thinking the problem and solving it with harder way, making it work and having it in use.

The easiest way to get it work, is keep it disabled by _default_ not by removing it, what has now done.
Lucky to us, Konqueror, Dolphin and many other application supports it and makes those applications even better because then those are more simple and cleaner to use when user can configure the application to adapt them, not user to adapt the application. 

The Dolphin and Konqueror has feature that when user hides menu, user gets it easily back when right clicks the file view/webpage and first one is "Show menubar Ctrl+M". Konsole has same thing but it is not first one, because konsole is used more by "advanced" users than novice users, so it cant be always the first option and in a way of them.

Just do a mockup of the menu hided on Amarok2 and compare it to non-hided menu version, it's nicer and cleaner for user, if only a few % of Amarok2 time of use, is using menu, why it should be there?

Just disable the shortcut and do not add the menu function for it and it's like now, but those who want to use KDE, not Gnome, can hide it.
Comment 3 Ljubomir Simin 2008-09-14 16:25:19 UTC
Well, if we disable the shortcut by default but leave it for power users to set it by themselves there's really no much space for users unwillingly hiding the menu. I'd say go for it. 
Comment 4 Mark Kretschmann 2008-09-14 16:32:10 UTC
Nope, absolutely not. We've discussed and decided this long ago, and we won't change it.