https://bugs.kde.org/show_bug.cgi?id=466107

Felix Ernst <felixer...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |felixer...@kde.org

--- Comment #4 from Felix Ernst <felixer...@kde.org> ---
>Maybe any state where the menu gets hidden should show a message
>telling the user it can still be accessed with the context menu, the same
>way there's a message that tells you the keyboard shortcut to bring back
>the menu.

I don't think this can be implemented in frameworks because it is up to the
applications to add the hamburger menu (or some other way to get back some sort
of menu) to their context menus. They could also have a button on the UI to
re-enable the toolbar, or they could decide that the toolbar is purely optional
in their application and wouldn't want to add anything to the context menu to
re-enable it or the menu. We also can't assume that the application would have
a menu bar so we can't advertise the Ctrl+M shortcut. Similarly we can't even
assume that the application has a toolbar because KHamburgerMenu doesn't need
to be placed on a toolbar, so we can't tell users about such an action either.

All in all, unless all right-clicks and all context-menu opening were to be
routed through KHamburgerMenu (which seems like a bad idea), I don't really see
a way to ever implement this in frameworks. -- Oh, even worse! I forgot that
the same issue applies for applications that don't even use KHamburgerMenu. We
would have to show a dialog for them any time the menu bar is hidden because we
can't know if a hamburger menu is implemented in the toolbar.

So, while I understand the basic argument, this might not be an actionable bug
report for frameworks.

I want to add though that if I (or anyone) doesn't see a way to technically
implement something, it might just be that I/they simply don't have the right
idea on how to accomplish something.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to