01-15-2013 06:01 PM
01-23-2013 09:09 PM
I have noticed some changes in the newer versions of Qt (4.8.4 and 5.0.0) which suggests that the situation will improve in the future. Maybe cascades will become available for the playbook sometime soon.
The problems I have experienced seem to be from the lack of a window manager. For example I found I need to manually set the active widget when a dialog is closed or it will stay visible most of the time (QWidget::activeWindow). Window resizing (portrait to landscape) is still ugly.
It seems that Qt on a Playbook has too many quirks to develop anything 'professional'.
01-23-2013 11:13 PM - edited 01-23-2013 11:14 PM
You might be interested in http://wiki.qt-project.org/QNX as well as the #qt-qnx channel on the Freenode IRC network. There are, indeed, people working on making things better (and working around what's not yet).
(Stop by #BlackBerryDev on freenode, as well, since it's a more active and generally-scoped channel [though since Cascades is the new shiny thing, that's what much of the conversation tends toward at the moment].)
01-24-2013 02:21 AM - edited 01-24-2013 02:21 AM
You will find the newer versions of Qt are much better than 4.8.3.
Especially the one that is included in Blackberry 10 firmware.
For now, I recommend just compiling Qt 5.0 for Playbook ( http://qt-project.org/wiki/Building-Qt5-for-Blackb
01-25-2013 07:32 PM
01-25-2013 08:40 PM
I have tried different versions of Qt (4.8.3, 4.8.4, and 5.0.0). I have actually compiled and installed programs using all three versions of Qt on my playbook (which I got for Christmas by the way). I was actually blown away by the entire process as I didn't expect any kind of success.
I have been using 4.8.3 lately because it has the least issues. The problems with the other two versions were real show stoppers:
I wasn't able to compile this version of Qt without modification of the source code as the functions navigator_set_orientation_mode() from <bps/navigator.h> don't exist in the playbook sdk. The modifications involved using functions from <bps/orientation.h> instead.
The end result was a fiery crash when the screen rotated which I couldn't find a way to prevent.
This worked the best for small test applications but when I tried something more substantial the application would SEGFAULT in libQt5Core.so (before it reached main()). I don't have a lot of experience debugging applications at this point in the initialization so I only got as far as finding where the problem occurs. This wasn't specific to qnx as it also happened on my desktop computers as well.