@JonB that works. Don't know why I didn't try that, other than getting lost in all the overloads that involved signals/slots. The simplest one with just a QString argument does the trick. Thanks!

Within a half hour of posting this, I stumbled upon the answer. I was thinking things were more complicated than they really were, and adding them to the group is as simple as this: OperationGroup->addAction( ui->actionManual ); OperationGroup->addAction( ui->actionAutomatic );

Apparently separator will always fill the height of the toolbar (or width for vertical toolbars). You can limit it by adding top/bottom margins, so if your toolbar is 40px and you want the separator to be 30px add 5px top and bottom margins.

Hi, You can use the QToolBar::toolButtonStyle property and set it to Qt::ToolButtonIconOnly.

@BigBen Also check out eventFilter. Here's a link to the documentation.

@SGaist said in QAction label with &: Hi, Double it and you should be good to go. Well that was anti-climatic... thanks! Solved :D

Issue can be found here : https://bugreports.qt.io/browse/QTBUG-98354

I see what you did. The WidgetAction acts as a container handling the shortcut. It is similar to a custom widget. As you said, it seems over complicated, so I will keep it simple for now, maybe by manually showing the shortcut in both actions, or in its parent.

@BDC_Patrick said in Get all Widgets of Type <Type> ?: But, this only works, if i put the code directly into the construct function of the Window itself (after ui->setupUi...). Why? It's QObject::findChilden(), you can use it for any widget. But, i thought more of a Function in a seperated file, that all Windows can make use of. If you really want it in a separate file then pass the parent widget as a parameter. Are you using Qt's support for cross-language?

If this is reproducible with C++, then C++ since the Python bindings are built on top of it.

Because we had declarations of shortcuts littered all over the place we came up with the following solution to handle them in one place. We derived a class MyApplication from QApplication and overrode bool notify(QObject *receiver, QEvent *e) override. Within this function we checked e->type() == QEvent::Shortcut. Everything that couldn't be handled is then forwarded to QApplication::notify. We didn't override the Ctrl+C shortcut or anything similar. However, because this is so early in Qt's signal handling you could be lucky with this approach.

@JoeCFD from the looks of it, it could be an Ubuntu specific bug.

Old lasting bug ... [image: Popup-1.png] [image: Popup2.png] Funny things happen in full screen ... In this screenshots you can see an another bug : the checkmark ✓ doesn't follow the font size of the menu. [image: Popup3.png]

@mrjj said in QMenu & QAction get sender button/widget?: Hi Why do you need to know the parent? QAction can be shared so the same function can be activated from multiple sources. But normally action does the same regardless from where is was triggered. I need to adjust action command parameters depending on the parent widget. I tried action->parentWidget() but it did not return anything I could use . Esentially I can have action that does A+B, and if the action is in global widget it would do just that, but if its in local widget then I will need localA + localB... more or less... thus the need to have a way to knowing parent widget while sending command to work. @Chris-Kawa said in QMenu & QAction get sender button/widget?: Instead of starting with the action you can connect to the menu's triggered signal. In the slot sender() will give you the menu and you can go up the parents with parentWidget() to find the toolbar if you need. Hmmmmm that looks very tempting!!! Will give it a go thanks! I was about to write my own action system to handle my needs but perhaps with Chris Kawa reply I can utilize native qt ones ! Thanks! BRB testing. Ok so this gets me half way there. I can now do quite a bit nice stuff with menu & actions, like changing menu default action to do something else based on action clicked and all that - yay ! But... how do I find out that menu parent - QToolbar or QToolButton? Is there a path down from there? And it looks like the toolButton has thesame triggered signal... hmmmm yep this is beautifull, it propagates all the way to toolButton where I can do what I want with the action and its data. Amazing, whoever designed that system is my hero.

@mrjj show me the right path and I found a solution. QToolButton:!checked { border: none; }

QObject are not copiable, see here for the why.

You said you're using QActions - just reconnect them to other slots depending on your current state.

Hi, In addition to @MrShawn, the slot can have less arguments than the signal, therefore you can keep their current signature.