Bug 200177 - Do net set shortcut for "hide menu-bar" by default
Summary: Do net set shortcut for "hide menu-bar" by default
Status: RESOLVED DUPLICATE of bug 168070
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-14 15:28 UTC by Matthias Fuchs
Modified: 2010-01-13 19:59 UTC (History)
2 users (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 Matthias Fuchs 2009-07-14 15:28:43 UTC
Version:            (using Devel)
Installed from:    Compiled sources

I think that no shortcut should be set for "hide menu-bar" by default.

Hitting Ctrl + M can be very confusing, the people who want that feature should set it themselves imo.

In my experience people (3) think it is some kind of bug or retry the key-combinations they pressed, having the option to deactivate in the context-menu was not intuitive for them.
Comment 1 FiNeX 2009-08-09 10:32:43 UTC

*** This bug has been marked as a duplicate of bug 168070 ***
Comment 2 Mirza 2010-01-13 16:34:14 UTC
@ FiNex

It seems to me that this bug report is exact opposite of the bug 168070 !
And you marked it as duplicate :S
Comment 3 FiNeX 2010-01-13 19:38:11 UTC
@Mirza: I think not: this one is specific to konsole, while bug #168070 is about having the same shortcut in all the apps. IMHO, if the shortcut should be enabled by default or not, is a subtask of that bug. At least a comment about enabling/disabling the shortuct could be added there.
Comment 4 Mirza 2010-01-13 19:59:30 UTC
@ FiNex
Although i can see what you are implying, i, however, do not see how this bug can ever be resolved by linking it to bug 168070.
One side says that every app should be able to hide menu bar Ctrl+M way or ony other way;
This side says Ctrl+M should not be default.

I am not saying you are wrong, i just don't see this bug ever being resolved properly by saying it is a duplicate, when only duplicity (i see) is that they are talking about the same feature, but are requesting different things.