Hi I think you action runs out of scope it seems to be local variable QAction actions[11]; and you take address of them so it does not copy but refernce inside the list listOfMenus[0].addAction(&actions[i]); but it looks to me like the actions[11]; lives in constructor and hence when Mainwindow is shown, they are all already deleted. Move the list to be a member of the class and see. Damn Pl45m4 beat me to it :)

@nland Did you ever figure this out?

@raven-worx Thanks, I will try that. I let you know if it works or not.

@ars1614 ok. never seen it then :) I would not rule out you can override it closing on menu selection by subclassing or using event filter.

ok this appears to be the same problem as this: https://forum.qt.io/topic/57647/qml-change-toolbar-color-one-style-property-only not really "solved", but at least some pointers in that previous post.

@mandruk1331 QDialog already provides all the signals (accepted() and rejected()) and slots (accept() and reject()) you'd need. You only need to call accept() when you've checked that the login is successful (meaning in the button slot). See my example in post #1 how to connect them! As to the login dialog implementation, something like this: class MLogIn : public QDialog { Q_OBJECT public: explicit MLogIn(QWidget *parent = 0); ~MLogIn(); private slots: void on_pushButton_2_clicked(); void on_pushButton_clicked(); private: Ui::MLogIn *ui; }; void MLogIn::on_pushButton_2_clicked() { //< Try logging the user in if (loginSuccessful) accept(); else QMessageBox::warning("No such user/password"); }

No, that's the native OS X menu so you can't modify it. Again: use the Info.plist file, it's also explained in QMenuBar's documentation

@onek24 For the benefit of anyone finding this post, I found a much simpler solution for attaching information to a menu action : void QAction::setData(const QVariant & userData) QVariant QAction::data() const I currently prefer it over the much heavier solution of implementing a custom QAction class.

Hi and welcome to devnet, 2 things: Why this QString::fromUtf8(tr("XXX").toLatin1()) instead of tr("XXX") in QAction constructor ?? Why this mainWindow.menuBar()->addMenu(fileMenu); at the end ??

You're welcome ! SInce everything is OK now, please update the thread title prepending [solved] so other forum users may know a solution has been found :) Also, while browsing the forum, consider up-voting the answers that helped you, it will make them easier to find for other users :)

It's working fine, i was nesting the MenuItem entrys and that didn't work Stefan

It's not Qt specific and that's how Windows worked from the time it was invented. The accelerators are keyboard navigation aid and they are not shown unless you use keyboard.

Maybe there's a widget that you didn't put into a layout? The default position of such widget is in the upper left corner and the 100px sound like some default size. Try adding this in your main: qApp->setStyleSheet("QWidget { border: 2px solid red;}"); This should put a red frame around every widget so you'll see if anything's there.

@silex92 Perhaps you should post some code to try the scenario.

ty, I have downgraded some packages (libglapi-mesa f.e.) and reinstalled some others. nopw everything is fine!

It looks like there might be an easier mechanism to do this kind of thing with in the future. Rather than writing my own MenuBar from scratch, the Qt team have implemented styling support for most of their components. Whilst i haven't tried this yet (I'm stuck on a different part of my project at the moment), MenuBar Style should be perfect for what I was originally trying to acheive, by writing custom delegates, with the appropriate behaviours attached to their properties.

@mcosta "Have rebuilt the same code with a different version of Qt?" - yes, I did it "Running both versions of the application on the same machine shows you different results??" - yes I guess something has changed in Qt sources since version 5.3 or 5.4. I hope this thing (to show menu shortcuts) is tweakable via Qt API.