MacOS Mavericks Issue...
My app is behaving differently when running it standalone vs via QtCreator on Mavericks.
All is well when I run from QtCreator (once I added the 'font hack' to get widget fonts to line up), but when I run the app standalone, the app is not initially activating. Also, something weird is happening when trying to run a process from within the app - I don't seem to be getting stdout/stderr feedback from the process. Both these issues go away when running the app from QtCreator.
I tried executing /Developer/Tools/Qt/macdeployqt on the app, but it doesn't help.
I also just tried upgrading to 4.8.5, but same problem.
Actually...looks like the app is activating at startup, but then immediately deactivating.[/edit]
Ok, looks like the app activation issue is my fault.
The app is started by a launcher with the 'open' tool, which seems to have some kind of race condition problem in Mavericks where if the launcher exits quickly enough, the launched app isn't properly activated.
AND, it looks like the process issue is something to do with current directory...
The current dir problem was this one:
ie: QDir::currentPath() is returning '/' on Mavericks. Easily enough worked around, but I do consider this a bug.
The bug report page seems to suggest 'this is the way Finder now works' on Mavericks. However, apps built with xcode still appear to start with the app's 'Resources' dir as the current dir which suggests this isn't the case.
[quote author="marksibly" date="1384048475"]The bug report page seems to suggest 'this is the way Finder now works' on Mavericks. However, apps built with xcode still appear to start with the app's 'Resources' dir as the current dir which suggests this isn't the case.[/quote]You may want to bring this to the attention of Qt engineers in the "Development mailing list":http://lists.qt-project.org/mailman/listinfo/development. If Qt programs are behaving differently from Xcode-built programs, then it's probably something to fix.