Qt issues on BB10
codenode last edited by
Aaron Adiri asked for list of issues with Qt on BB10, what is missing, where are errors to be fixed etc.
He'd like to have an overview till QtDevDays...
So, the issues I have found sofar:
QFeedback and other parts of Qt are still missing on BB10, also Sensors are not supported by the simulator (at least QMagnetometer), so that you'll need a device to get your App running with it.
Someone else already pointed out that QClipboard is missing too: http://supportforums.blackberry.com/t5/Cascades-Development/How-to-watch-for-Clipboard-changes-BB10-multitasking-issues/td-p/1943889
Edit: Link fixed.
Thank you for creating this thread, codenode.
Yes, QClipboard is the problem I have currently at BB10.
But there are a lot more differences which forces developers to put #ifdef in their code everywere. I'm nearly to say currently are only the essential stuff integrated to use Cascades on top of Qt/qml, no Libraries for which similar stuff already exists in the BB native NDK. This affects mostly QtMobility.
The drawback of this, creating portable and clean code is nearly impossible. Also the Signal Slot concept of Qt gets broken which leads often to more ugly and power consuming code.
narnaud last edited by
bq. Also the Signal Slot concept of Qt gets broken which leads often to more ugly and power consuming code.
What do you mean by broken?
Signals/slots should work just fine on BB10.
[quote author="narnaud" date="1350291617"]bq. Also the Signal Slot concept of Qt gets broken which leads often to more ugly and power consuming code. What do you mean by broken? Signals/slots should work just fine on BB10. [/quote]
You're right. But the native C++ libraries of the BB10 NDK doesn't provide QSignals. And without those the Qt developing paradigm of Slots and Signals doesn't work.
Same goes to stuff like QString if it goes to multilanguage and multiencoding support.
Edit: If your app doesn't need to communicate with the outside you're fine. If you need more (sensors, calendar, clipboard, messaging, settings) you have to find workarounds, wrap libraries yourself and use power consuming polling instead of a simple signal.
New Issue, this time at ListView's:
There are functions like scrollToItem and scrollToPosition but no way to check where in the list you are currently, what is the current position or which Items are currently visible.
Bomb3rman last edited by
Just a few things. QClipboard is working (with certain limitations) and only in pure Qt applications. For cascades apps there is a separate library. Also settings should work just fine. The QtMobility stuff is currently being implemented. I know that a lot of the Qt mobility parts are still missing, but it is getting there. And help is always appreciated: http://gitorious.org/+kdab-developers/qt-mobility/qnx-qt-mobility
@helex: Are you talking about a QtQuick ListView or a Cascades ListView