https://bugs.kde.org/show_bug.cgi?id=501871
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Product|kwin |frameworks-kconfigwidgets
Assignee|kwin-bugs-n...@kde.org |kdelibs-b...@kde.org
Summary|[Feature request] Global |Global menu being enabled
|menu enabled removes |should remove hamburger
|hamburger menu on kde apps |menu button
Component|general |general
Status|REPORTED |CONFIRMED
Version|unspecified |6.12.0
CC| |felixer...@kde.org,
| |n...@kde.org
--- Comment #1 from Nate Graham <n...@kde.org> ---
Yeah, it makes sense to only have one menu structure visible, not two. This is
the reason why we automatically hide the hamburger menu button when the
in-window menubar is visible.
In QtWidgets apps, we could make KHamburgerMenu hide itself when it detects a
global menu.
For QtQuick apps, typically the hamburger menu is custom; unfortunately there's
no standard base class they all inherit from, so we'd have to implement this
logic in every app (or create a common base class for them to all inherit from,
and then implement it there).
Let's use this bug report to track it for KHamburgerMenu. Please open a new bug
report for every QML app you'd like to see changed (I'm sorry, I know this is a
lot of work)
--
You are receiving this mail because:
You are watching all bug changes.
