Hey Mirko,

Nothing concrete implemented yet but there is a code sample of how to add it to your apps here [bugreports.qt-project.org]

Hopefully this will make it into the Qt5 Mac OSX port.

All the best,

Sean

Hopefully it will make into 4.8.x too!

<rant>
It’s embarrassing that all new, useful stuff and even bugfixes are going into Qt 5 first, if not only. Qt 5 is far away from being prime time and the vast majority of user base, at least when talking about serious projects, are going to use Qt 4 for a long time in the future. Looking at the broken 4.8.0 release – it was by far one of the worst in years – I would expect many developers to consider switching not before Qt 5.1 has been released.
</rant>

Yeah. I agree. The problem is that I don’t know if there will be a 4.9.x release and the Lion full-screen support would count as a new feature and so can’t be added to 4.8.x. The 4.8 release certainly does have a lot of issues on Mac OSX.

Not only on the Mac, but that drove me nuts, yes, and I seriously considered staying at 4.7.3 (as 4.7.4 has a serious bug in QTextEdit).

The tarball contains bin/syncqt and bin/syncqt.sh, wich leads to build errors on windows, where you usually do not have perl installed.

My overall experience is that Qt 4 quality deteriorates with everyone being busy with Qt 5. This was not the case during the move from Qt 3 to 4.

And additionally, now with open gov in place, one could theoretically send patches much more easily than ever. Only if they wouldn’t expect to send a patch against Qt 5 at first and eventually (or not, who knows?) cherry picking that for the 4.x series. Come on – as if a serious developer doing day by day business with Qt 4 is eager to setup a Qt 5 development environment only to send in a trivial patch that changes 4 lines. This can’t be serious. This is surely not the way to motivate possible candidates to contribute to Qt. While developing Qt 5 is exciting for those involved, the majority of the crowd plainly doesn’t care yet.

Thanks, Sean and Volker.

I agree to the sentiment that 4.x is left behind a bit. On the other hand, Lion is not officially supported in 4.8 still, and those are Lion APIs. I prefer having full Lion support in 5.0 over half done support in 4.8.

How far is Lion and it’s new APIs supported in Qt 5 as of yet, does anybody know?

Honestly, I would prefer that Qt 4 would get enough love to be healthy for the next years. The migration won’t be finished by 2013 and all the Qt 4 code base doesn’t matter then. But I don’t count too much on the community here, adding that stuff to 4 seems to be neither sexy nor fun. Hopefully Digia will be more sensitive to developers’ needs here.

Agreed. I am a bit curious to see where Mac support is going in general.

I can inform you that a team of engineers from Nokia and KDAB are working on Mac OSX support for Qt5. This will all be done in the public so keep an eye on the repositories.

I am not sure what is going on with Qt 4.8.

I just got a MacBook Pro too so I would also like to see the support improved ;-)

Nice :-) Watching you…

Any news here?

I’d love to see more work by Nokia in Qt Desktop (and less focus on QtQuick QML candy stuff).

Will the Lion full screen work in Qt 4.9?

There is no 4.9 planned but Lion full-screen support is already in Qt5.

I would also like to see proper OpenGL Core Profile 3.2 support in 4.8 at present it doesn’t seem to work for me (always falls back to the default 2.0) I have a work around for my own code but don’t plan to move to 5.0 until the year after as I have to use it for teaching and don’t like changing half way through an academic year.

I like ;-)

ZapB wrote:

There is no 4.9 planned but Lion full-screen support is already in Qt5.

Hi umm so should this be in Qt5 now? I assume this’d be referring to QWindow::showFullScreen() which certainly isnt working for me at the moment.

Although I spotted this: https://github.com/bjorn/tiled/pull/118

I’m using:
Mac OSX Lion 10.7.5
QtSDK 5.0.1

- Matti