[KDE/Mac] Review Request 120149: [OS X] improved menubar experience: protected Preferences menu and cleaner "system tray"

René J.V. Bertin rjvbertin at gmail.com
Tue Sep 16 12:47:47 UTC 2014



> On Sept. 15, 2014, 2:19 p.m., Thomas Lübking wrote:
> > kdeui/actions/kaction.cpp, line 164
> > <https://git.reviewboard.kde.org/r/120149/diff/2/?file=312029#file312029line164>
> >
> >     would this eg. work with kwrite ("Configure Editor...")? - or other kpart driven things?
> 
> René J.V. Bertin wrote:
>     The question is, should it work? KDevelop for instance has a Configure Editor item in its Settings menu, added *before* "Configure KDevelop...", and in that case it's not the editor's configure dialog that should get linked to the Preferences menu item.
>     If kwrite is nothing but a wrapper around an editor kpart (kate?) then I guess the end result will depend on how that kpart creates its configure action... If it uses KStandardActions and the wrapper (kwrite) doesn't (or only does after the kpart did), the Preferences menu ought to link to "Configure Editor...".
>     
>     In short, it's neigh impossible to cater for all possible cases. In a sense it wouldn't disturb me at all if KDE applications simply used their own menu organisation, but it's Qt that obliges us to take action because otherwise it's there that the organisation can get messed up.
> 
> René J.V. Bertin wrote:
>     This is where Qt initialises `menuRole` with `TextHeuristicRole`, a value only used on Mac:
>     
>     Qt 4.8.6 :
>     
>     	QActionPrivate::QActionPrivate() : group(0), enabled(1), forceDisabled(0),
>     	                                   visible(1), forceInvisible(0), checkable(0), checked(0), separator(0), fontSet(false),
>     	                                   forceEnabledInSoftkeys(false), menuActionSoftkeys(false),
>     	                                   iconVisibleInMenu(-1),
>     	                                   menuRole(QAction::TextHeuristicRole), softKeyRole(QAction::NoSoftKey),
>     	                                   priority(QAction::NormalPriority)
>     
>     Qt 5.3.1:
>     
>     	QActionPrivate::QActionPrivate() : group(0), enabled(1), forceDisabled(0),
>     	                                   visible(1), forceInvisible(0), checkable(0), checked(0), separator(0), fontSet(false),
>     	                                   iconVisibleInMenu(-1),
>     	                                   menuRole(QAction::TextHeuristicRole),
>     	                                   priority(QAction::NormalPriority)
>     
>     
>     Overriding that one way or another will make KDE menu(bars) behave exactly as they do on Linux, with only a few OS-specific items in the Application menu (Hide, Hide others, Show All). The added benefit would be for KDE applications like `konsole` that do not use the global menubar.
>     
>     Does KDE have a particular/special status making it easier to propose changes to the Qt API?
> 
> Thomas Lübking wrote:
>     > Does KDE have a particular/special status making it easier to propose changes to the Qt API?
>     
>     dfaure, I assume ;-)
>     
>     No - not really. None that i'm aware of.
>     Would it help to alter KStandardAction::preferences() to explcitly set the PreferencesRole for this one (ie. would an explicit PreferencesRole trump TextHeuristicRole hitting for "configure shortcuts" or similar?
> 
> René J.V. Bertin wrote:
>     I've dug into the Qt code (4.8.6 for now), and am now seeing how far just removing the guesstimating on the About and Preferences will take us. 
>     
>     `KStandardAction::preferences()` *already* sets PreferencesRole, that's one reason I moved up the setText call to before the block that sets the MenuRole (even if ATM that indeed doesn't change a thing).
>     And that works ... as long as `KStandardAction::preferences()` is called before any other menu actions are added to a menu. It's the first action that gets added and that matches Qt's heuristics that ends up under the Preference menu item. I'm hoping this is limited to the items of menus belonging to the the global menubar, but I haven't traced the underlying code in full detail so it could even be that any menu action/item could end up there.

https://bugreports.qt-project.org/browse/QTBUG-41351


- René J.V.


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/120149/#review66546
-----------------------------------------------------------


On Sept. 15, 2014, 1:03 p.m., René J.V. Bertin wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/120149/
> -----------------------------------------------------------
> 
> (Updated Sept. 15, 2014, 1:03 p.m.)
> 
> 
> Review request for KDE Software on Mac OS X, kdelibs, KDEPIM, Marco Martin, and Olivier Goffart.
> 
> 
> Repository: kdelibs
> 
> 
> Description
> -------
> 
> This review is for 2 sets of changes; an initial one to the way "system tray" are rendered, and a newer set that protects the Preferences menu from getting linked to any action with an appropriate title.
> 
> -- the system tray:
> Until now, "system tray" menus had some rendering issues on Mac OS X:
> 
> - The menu title, the 1st menu item that on Linux shows the application name, remained empty
> - Menu items that can (in principle, potentially) show an icon always showed the icon
> 
> Point 1 was resolved by emulating the Linux addTitle/setTitle action in `KStatusNotifierItemPrivate::init()` : the menu title is implemented as a deactive standard menuitem followed by a separator. This makes the item stand out on a GUI that doesn't support the kind of formatting in menus as used in the Linux implementation.
> 
> Point 2 was identified as a Qt issue: `isIconVisibleInMenu` is ignored for systray menus. It was resolved by adding `KMenu::addAction` methods that overload the ones from QMenu that were hitherto inherited unchanged by KMenu. The only different method is `addAction(QAction*)` which removes the icon from the `QAction` if `isIconVisibleInMenu()` is false. The other `addAction` methods are "overloaded with themselves" with `using QMenu::addAction;` in the header file.
> 
> -- the Preferences menu item
> This is a menu item living in the Application menu, a menu that sits in the menubar between the Apple (?) menu and the File menu. This menu also contains the Quit command.
> KDE and Qt applications typically do not set up their menus in this fashion, so Qt provides an automatic way to put relevant menu items (actions) in the Application menu, using Apple's naming. The algorithm is described under QMenuBar in the Qt documentation: for the Preferences action, it will consider any action that has a text containing `config`, `options`, `settings` or `preferences`, and put it under the Preferences label if its menu role is set to `heuristic` (which appears to be the default).
> In practice, many applications provide a series of menu actions with names that trigger this method, and they do not always create their own preferences/settings/configuration menu first. Yet it is the first menu action that matches that will be installed under the Preferences menu, with the Command-, shortcut. A good example is KDevelop: it will have a Preferences menu that activates the `Configure Selection` action - which does not open a settings dialog but launches the configure or cmake procedure for the selected project ...
> 
> My proposed solution overrides this Qt behaviour. On OS X, the `KAction(const QString &text, QObject *parent)` constructor calls a modified (static) function `setTextWithCorrectMenuRole` which checks the text against the patterns Qt will consider for `PreferencesRole`. If it finds a match, it will force the role to `NoRole`, unless it is a perfect match with the standard KDE configuration action for the application (`"&Configuration appName..."`) in which case it sets the role to `PreferencesRole`. This latter consideration allows kdelibs to "catch" the configuration menu for applications like KMail, which appear not to be created using KStandardActions.
> This approach can be extended to other menu actions that end up incorrectly in the OS X Application menu.
> 
> Applications that create menu actions using QAction or a different KAction constructor will see no change (and should use `setMenuRole` selectively on OS X).
> 
> 
> Diffs
> -----
> 
>   kdeui/actions/kaction.cpp 9e8f7fb 
>   kdeui/actions/kstandardaction.cpp 7de0c6f 
>   kdeui/notifications/kstatusnotifieritem.cpp 1b15d40 
>   kdeui/widgets/kmenu.h f96e263 
>   kdeui/widgets/kmenu.cpp 7dab149 
> 
> Diff: https://git.reviewboard.kde.org/r/120149/diff/
> 
> 
> Testing
> -------
> 
> Testing was done with kdelibs git/master and KDE/MacPorts on OS X 10.6.8 . The modified code is in compile-time conditional blocks used only on OS X, so no regressions are to be expected on other platforms.
> 
> KF5 is not production ready on OS X, so I am not currently able to port these modifications beyond KDE4. However, I did see that Qt5 has a new approach to adding titles to menus, which can be described as a "labelled separator". Backporting that function from the Qt5 source to kdelibs gave menu items that had the separator but not the text (title) label. It is thus likely that some kind of emulation will also be required with KF5, on OS X.
> 
> I considered doing the addTitle/setTitle emulation in kmenu.cpp, but decided against that for now. Menu titles are rendered as under Linux in menus that are not attached to the OS X toplevel menubar (say in context menus). Without knowing how to distinguish the kind of menu in KMenu methods the emulation will have to remain in the client code.
> 
> The Preferences menu protection should carry over easily to KF5, supposing Qt5 uses the same heuristics to place relevant menu actions under the OS X application menu, and supposing `KAction` has made the transition to KF5.
> 
> 
> Thanks,
> 
> René J.V. Bertin
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-mac/attachments/20140916/183965a4/attachment-0001.html>


More information about the kde-mac mailing list