Mac Menus are not active ????

sandy.martel23

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

Nevering

Well not found in my actual application. that has sever folders were files are being used for building aspects of the application.

sandy.martel23

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

why ?

Gui applications on Mac are bundles.

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

Look at how to embed resources, either the Qt way, with the 'Qt Resource Compiler' or the Mac's way with bundle resources.

If you really want to keep those as external files you'll need to adjust the relative path on Mac.

Nevering

is this a good reference, or is there a better one, this is from 4.8.

http://doc.qt.io/qt-4.8/deployment-mac.html

Rondog

I ran a test and saw exactly what you described in this thread (Qt 5.6.0, OSX 10.10.5, XCode 7.2.1). I tried changing a few things here and there in the source to see if I could get it to work without success. Changes in the PRO file seemed to affect it.

In the project file I remove this line:

CONFIG -= app_bundle

and replaced it with this:

CONFIG +=release \
		warn_on \
		qt \
		thread

It worked fine after this change for some reason.

I didn't look into what the differences are in these options of the project file. These are common options I use for everything. Maybe try this and see if this works for you as well.

I also tried converting the UI file into a set of cpp files (generic main.cpp, mainwindow.cpp, and mainwindow.h). It worked regardless of the above change in the PRO file.

It looks like there is something odd going on but I am not sure what the source is. The project file supplied with this sample should be cleaned up regardless (maybe this is the underlying reason?). The project file from the CPP generated version is a little more complete so this could be a reason I didn't see this problem with the derived version and only with the UI version (?).

Nevering

Someone please help me understand the problem. Why did CONFIG -= app_bundle cause the problem and removing fix it? The article linked above says that CONFIG -= app_bundle should be used for Macs .

Nevering

@Rondog

So the article that I linked says that CONFIG -= app_bundle is needed on Mac.. Is this not the case ? Is there any more recent documentation on how to build the bundle within Qt?

SGaist

You misunderstood the documentation. As stated just about the code snippet, the CONFIG -= app_bundle line applies only to command line tools.

Otherwise, use a bundle. macOS looks for information in that bundle: the Info.plist file being the central point of interest. Qt generates one for you automatically with sensible defaults.

Depending on what feature you'll be using, you will have to provide your own file.

Nevering

Trying to find out more, but I don't see any info.plist created with any of my projects built on my Mac.

SGaist

Where did you look for it ?

Nevering

@SGaist

I saw it in the Mac documentation.. And I did a search on my Mac. There doesnt' seem to be any related info.plist file generated in the local folder. However there are some on the system and in the Qt example folder. Still trying to figure this out, documentation on this would really help ...