Mac Menus are not active ????

SGaist

Sorry, I missed your answer.

I can't reproduce your problem because in the code you provided there are unknown elements: MenuInfo, itMenu and mainMenu.

Sure you can debug Qt, the source is freely available either be cloning it with git or downloading the sources from the version you installed on your computer.

Before stating that there is an obvious bug, please provide a minimal compilable example that reproduce the behavior.

Also, please note that this forum is community driven so there might not be many people here having the same hardware/OS version as you at hand.

Nevering

i understand that this is a community forum, but a bug that compromises cross platform to Mac would seem to be of huge concern . I did some researching and it seems that this problem was reported in 4.8. I can't find it right now, when I do I'll give a link. Apparently, it's been around for awhile, yet still alive and well.

Rondog

I haven't noticed this problem (I currently use Qt 5.6.0, OS X 10.10.5, XCode 7.2.1). It could be something new with Qt 5.7.x but I hadn't seen anything like this in previous versions (your hint that it might have existed since 4.8.x). I don't use a lot of menu's or complex menus but I do have menu's in some applications and they do work (I even double checked to make sure). I have never had an issue running these on any version of OS X that I have had (snow leopard and up) or at least anything that was noticable.

As @SGaist mentioned can you provide a minimal example showing this problem.

In your sample code is it possible that 'menuTitle' is an empty string in some cases and maybe this is why the menu is not constructed?.

MenuInfo menuInfo = itMenu.next();
QString menuTitle = menuInfo.getTitle();
if (!menuTitle.isEmpty())
{
   // create menu skipped if menuTitle is empty
}

kenchan

I too have an application that runs on Mac and Windows and have never seen the behaviour you describe. As other folks have said it may be a 5.7 regression but it must have been fixed since 4.8 or Rondog and I (and probably many others) would surly have noticed it.

As Rondog and SGaist suggest, you should show more code so we can reproduce the issue. It is better to provide a minimum app with a main window and the menus set up the way your app does it.

Do you get the same problem when you build the MainWindow example or the Menus example for instance?

Nevering

@Rondog

@Rondog said in Mac Menus are not active ????:

I haven't noticed this problem (I currently use Qt 5.6.0, OS X 10.10.5, XCode 7.2.1). It could be something new with Qt 5.7.x but I hadn't seen anything like this in previous versions (your hint that it might have existed since 4.8.x). I don't use a lot of menu's or complex menus but I do have menu's in some applications and they do work (I even double checked to make sure). I have never had an issue running these on any version of OS X that I have had (snow leopard and up) or at least anything that was noticable.

As @SGaist mentioned can you provide a minimal example showing this problem.

In your sample code is it possible that 'menuTitle' is an empty string in some cases and maybe this is why the menu is not constructed?.
MenuInfo menuInfo = itMenu.next();
QString menuTitle = menuInfo.getTitle();
if (!menuTitle.isEmpty())
{
   // create menu skipped if menuTitle is empty
}

The menu is constructed and displayed. It's just inactive until clicking on another program and then back to the this Qt app. It only has 2 menu items the default one on Mac and the one created in code.

SGaist

Then, please, provide us the means to reproduce that situation.

We are already several people not getting that problem. Therefore without your code we cannot help to either find the bug that you might have uncovered in Qt or find the one that you have in your application.

Nevering

I'm trying to put something together. It seems like if I have a .ui file for the mainwindow and use the ui-> things seem to work, if I don't then that's when the problems seem to appear. I'm trying to make a small example.

Nevering

I have tried to reproduce this problem with smaller subsets of code and cannot. I not really sure how to debug this problem.

I've rebuilt the project from scratch adding items and testings as I went along. Everything worked fine up the the point of adding a resource file .

Currently I have only the default Mac menu item, everything else is on the toolbar and working. All the application works except for the menu being dead until clicking on another program and then back.

mrjj

@Nevering
If you have a sample that can be built and tested,
please upload to git or any other site where
its easy for people to get it as one zip/together easy to run project.

That way its very likely that others will try your test program and we can find out if
its just on your system or its actually a Qt bug :)

Nevering

I was able to reproduce this in a small test project. I don't see a way of uploading a zip file

sandy.martel23

@Nevering

Once your menubar is created, add those 2 lines:

// Qt5.6: this seems to force the previous menubar to show up and activate
auto m = new QMenuBar; 
m->deleteLater();

This create another parentless top-level menubar and delete it later. I've been debugging through Qt's macOS menu handling code and it seems to have changed a lot between Qt5.5 and Qt5.6. This code triggers the native menu bar synchronisation that used to happen automatically. Looks like they screw this up for 5.6.

Nevering

Thanks for the answer, but that didn't help.. Still got a hang

Nevering

added it like this

ui->setupUi(this);
QPixmap pix(":/images/user.png");
QIcon ico(pix);
ui->toolButton->setIcon(ico);

auto m = new QMenuBar;
m->deleteLater();

I'll try again after the ui->setup

Nevering

Same thing

sandy.martel23

@Nevering
A test project would be great.

Nevering

I think I've added the code here ??
https://github.com/Nevering/Splitters.git

sandy.martel23

@Nevering
"This repository is empty."

Nevering

There now, please try again
learning github

sandy.martel23

@Nevering
Well, it's pretty simple in your case, don't do:

CONFIG -= app_bundle

Nevering

why ?

If I don't the files in the subdirectories are not found