Bug 202389

Summary:	Global Ctrl-M Hide-Menu Option
Product:	[Unmaintained] kdelibs	Reporter:	Bertel King, Jr. <kmetamorphosis>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	bluedzins, finex, majewsky
Priority:	NOR
Version First Reported In:	0.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Unspecified
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Bertel King, Jr. 2009-08-03 15:00:51 UTC

Version:            (using KDE 4.2.4)
Installed from:    Ubuntu Packages

Certain KDE applications (Dolphin, Konqueror, Gwenview, Kopete, etc) offer the option to hide the menu. However, this option seems to be up to the whim of each application to implement. Is it possible to implement a global setting in which Ctrl-M hides and unhides the menu? This spares each developer from having to implement it into their application. 

For those concerned about new users hiding the menu by accident, there can be the traditional popup saying "You have hidden the menu, press Ctrl-M to unhide it again" with the standard "Do not show me again" checkbox. 

Menus are a great way to store a large amount of features, but they are only needed for a fraction of the time a person spends interacting with an application, and during the rest of the time they use unnecessary pixels/add clutter to the screen. Those applications that currently use Ctrl-M to hide menus offer an unobtrusive solution.

Comment 1 Stefan Majewsky 2009-08-09 03:03:21 UTC

I'm astonished that this was not reported earlier, given all the buzz that was already created on this topic (e.g. on the Dot). Is this really not a duplicate of some earlier bug?

Comment 2 Bertel King, Jr. 2009-08-09 07:39:44 UTC

I originally filed this as a Kwin wishlist item (oops, I didn't know), so it wasn't a duplicate of any of the results that appeared. Also, nothing shows up when I click "Search for Duplicates" on this page. If this is a duplicate, I apologize.

Comment 3 FiNeX 2009-08-09 10:13:26 UTC


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