Right, I forgot that part. The "workaround" is explained in the QKeySequence documentation linked from the QShortcut one.

Glad you found a solution ! Would you mind sharing the changes you made ? You might even consider including them in Qt directly ?

@kenchan - Again, thanks. I've successfully used -Wno-missing-braces on the analyzer and editor, so it 'works' for at least some versions of the compiler. As for 'warn_on'/'warn_off', I had no trouble verifying their existence/function once I found them in the .pro file, but I had no prior warning to look for such a thing. I've been looking for QMAKE_CXXFLAGS, not weird macros that are defined in some middle ground between the .conf files and the .pro files. I don't understand how the .conf files work, much less how to successfully invoke half of the options documented there and elsewhere. On the other hand, I think that I've solved my main issue with the discovery of the hidden 'warn_off' in my library's .pro file. I have compile warnings again. More than I'd like, true, and I don't seem to be able to turn off specific warnings, but fixing the autogenerated code should get rid of the majority of the offending bits, so I can at least have some confidence in my builds again.

It does look like a similar issue. I was able to find a workaround thanks to this bug report. Setting the target OSX version to 10.12 in CMake did the trick.

@SGaist, could You provide an example please - fixed mylibrary.pro? Thanks!

Ok, thanks for testing !

Did you install Xcode 8 ? Your other error comes from the fact that you are calling xcodebuild in the folder where it's located and not where a Xcode project can be found.

@KevinD said in Modal from a modal (Mac): Hi, Don't use these two: box.setModal(true); box.setWindowFlags(box.windowFlags() | Qt::Popup); You're calling QDialog::exec which is for modal-only dialogs, and Qt::Popup isn't for dialogs, leave the window flags be. If you prepare a MWE (the download-and-build type) I can test on Linux (I have no Mac, sorry). Also you might consider filing a bug report if everything else fails. Kind regards.

@SGaist That worked, thank you so much! One issue I may have however is that my main project is written in C++ and when I compile it in Objective-C++ with cmake (adding -x objective-c++ to compile flags), I get all sorts of errors with interpreting the generated .o files. I'm going to google around a bit with what I've learned here and see if I can make it work.

Then one thing you can do is disable all your widgets and enable them one by one until you have the bug starting again.

Hi, IIRC, calling winID should give you the NSView and you can call window on it to get the NSWindow contained. Hope it helps.

thanks for your help, I have tried to edit my odbc.ini the Mac refused to save the file... That's why I gave up. As an intern, it's my tutor training who said to me to look at a native component. But if I can't find any solution I will come back to the first idea :)

This can be marked as solved.

Probably because on OS X the default menu bar is provided by the OS. See QMenuBar's documentation for more details. However I don't know if it's an OS X specific behavior of Qt Creator.

Might not be completely intuitive. That something you can bring to the attention of the NodeBB folks :)

@jsulm You're right. I don't know why I didn't think of that I filled in a bug report regarding this issue here: https://bugreports.qt.io/browse/QTBUG-51728

Now brochure in English available. http://www.labcsp.com/

Good ! Since everything is working now, please mark the thread as solved using the "Topic Tool" button so that other forum users may know a solution has been found :)

Hi and welcome to devnet, What sources did you download ? You have an option in the installer to get the sources that matches your installed Qt. If you take the time to search the forum, you'll find several threads about the MySQL plugin and OS X.

Hi and welcome to devnet, AFAIK from the Chromium project, builds for 32bit Macs have ended by the end of 2014. Snow Leopard was the last version supporting 32 Bit processors.

Some added notes from the trenches: Above, I describe a small stub setup that downloads a larger payload. However, if your payload is large from the server, you're going to be looking at the screen stuck at the "Running package scripts..." notice and a jammed progress bar while it continues to download over Curl your larger payload. One solution to that in your preinstall Bash script is to do this: osascript -e 'tell application "System Events" to set visible of process "Installer" to false' That super neat trick hides the installer so that you can show something else. That way, the customer doesn't think your installer just jammed. Then, build yourself a simplistic ObjectiveC application that looks just like that Installer but shows a more active progress bar (use a timer) and then displays a few messages like "Downloading..." and "Finishing download..." and stuff like that. Of course, you can do it in Qt, but even the most minimum Mac-based Qt widget app (not statically compiled) is 8.9MB zipped, whereas in ObjectiveC you can make an app that does the same thing in a mere 32K (unzipped). (Oh, and for you QML die-hards out there, a widget-based app has you topped on file size. I was seeing 12.1MB zipped for something comparable in QML.) Once that Curl has finished, it can then kill the ObjectiveC process and reverse the osascript to get the installer to show you the Finish page. If deploying a large commercial application, and especially if you need to hook up special high-permission items and require script control, then you may not want to use either the .pkg or .dmg formats at all. This is because, psychologically, customers are not likely to want to download a huge honking 200MB+ DMG or PKG file. Instead, they would be more likely to download a smaller file, run it, and then when it says Installing, it does the rest of the download steps. (I know it's the same wait time, but psychology is important in product marketing.) Take a look at Norton's Antivirus for the Mac. (There's a free trial on their website.) They basically made an ObjectiveC / Cocoa application and then zipped it. However, it's a stub setup that's very small. When you run it, it then shows the typical EULA and then starts downloading components from the web, and putting things into the appropriate places.

Just thought of something: you are trying to cross-compile a linux kernel on OS X. You should rather create a virtual machine using e.g. VirtualBox and do everything directly form Linux. That will save you time.

@jsulm Well, texts are not displayed but height of toolbar is too large.

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

@raf924 said: @ashishbansal http://doc.qt.io/qt-5/qdesktopservices.html#openUrl it's still available. Why would you think it was not? or did you know it was but wanted an alternative anyway? Sorry, I din't know that it's still available. I was searching for opening a local directory in qt and found somewhere calling it as "deprecated" solution. Anyway Thanks :)

You can find additional information in the qmake platform notes

So I finally found a part in the documentation saying: PRE_TARGETDEPS Lists libraries that the target depends on. Some backends, such as the generators for Visual Studio and Xcode project files, do not support this variable. Generally, this variable is supported internally by these build tools, and it is useful for explicitly listing dependent static libraries. Apparently I have to include the lib manually in the .xcodeproj file. That worked, but isn't Add Library... supposed to add the necessary commands to the .pro file?

@jcelerier said in Rendering performance problems on iMac with Retina 5K: https://bugreports.qt.io/browse/QTBUG-61384?focusedCommentId=361794&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-361794 . That one.

Thanks for the help. But the real reason was that, I was using wrong version of QT for my project. My project supports QT version upto 5.4 & I was using 5.5. After downgrading all works fine now.

@SGaist Thank you very much, I used the work-around they proposed (storing a copy of the certificate in the local resources of the app & adding that to the default CACertificate list before opening the socket) I'm afraid this won't be a clean long term solution though (the certificate will stay valid for a while, but eventually expires I guess). If anyone has any idea's for a more clean/permanent solution I'm very much open to suggestions. In the mean time this will have to do. Thanks again, I appreciate the comment

The latest development is that I had over 254 files open at once. No wonder nobody else had encountered this.

Thank you very much for all the advice. If anyone encounters a similar issue, I managed to solve the issue in this manner. No changes to the '.pro' file. using this code to reference the file-path. QFile dayfile(QCoreApplication::applicationDirPath()+"/days.dat") again thank you for pointing me in the right direction!

They do but I guess that since CoreAudio comes before PulseAudio alphabetically, it's the one getting selected.

@Almer_Cz said: ...and also create .pro and let qmake to generate XCode project, but this will produce a lot of Mambo Jambo around and won't be handy when something changes. So your looking for a way to create and maintain the Mambo Jambo manually and this will somehow be more handy ?