In my opinion, there is no need for the Momentics IDE. I have not bothered to even run it yet.
I would suggest just using the Qt SDK with the built in simulator to develop and test your app. Then you will not have to worry about the moc files etc. as they are all handled by Qt IDE. Then just build and deploy it via the command line to your playbook. (https://bdsc.webapps.blackberry.com/android/downlo
I have heard rumor that debugging on the playbook from the Qt IDE will be supported soon too...
Good luck!
Jon
Hello again!
After finishing with the Calculator Example I decided it's time to try the Application Example ( https://qt-project.org/doc/qt-4.8/mainwindows-appl
I've created a new project and did everything the same as for the Calculator. The different thing was a resource file, application.qrc. This one should be picked up by the following line of code:
Q_INIT_RESOURCE(application);
But for this to happen the qrc file needed to be compiled by the Qt Resource Compiler, rcc. Similar to the moc, right? So I've added a custom build step for the application.qrc:
- Custom Build Step Applicability: Apply Custom Build Step Overriding Other Tools
- Output file name(s): application.rcc
- Command: rcc -o src/application.rcc ../src/application.qrc
Unfortunatelly this custom step did not execute. What changes are needed to force the compilation of .qrc files? My workaround was to rename the application.qrc to application.h and to have it compiled as aresource to application.cpp:
- Custom Build Step Applicability: Apply Custom Build Step Overriding Other Tools
- Output file name(s): application.cpp
- Command: rcc -o src/application.cpp ../src/application.h
This works because the file generated by rcc is a C++ source file containing the data specified in the resource file.
And hooray! Here is the Application Example in the simulator:
Dumi.
Back again! And with a serious problem I've been trying to overcome in the last hours. The Application Example saves the size of its window when receiving the close event. Unfortunatelly this happens only when selecting File->Exit. When closing the application in the BlackBerry way the close event is not raised. And that's because that event is the navigator exit event.
Still, there is a Qt event that may be used for this purpose - QEvent::ApplicationDeactivate. To have access to this event I have created a new class, MyApplication, that overrides some of the QApplication behaviour:
bool Application::event(QEvent *ev) {
qDebug("%d", ev->type());
if (ev->type() == QEvent::ApplicationDeactivate) {
// do something
}
return QApplication::event(ev);
}
Is this the right way? It might be if you just need this navigator event.
But what if you need some other navigator events? Like navigator swipe down, navigator orientation, navigator window active/inactive? How should this be accomplished?
First thing that came into my mind was to create another class where to listen for bps navigator events. I've extended QThread and implemented the following:
NavigatorEventsThread::NavigatorEventsThread() {
bps_initialize();
navigator_request_events(0);
stopped = false;
}
NavigatorEventsThread::~NavigatorEventsThread() {
bps_shutdown();
}
void NavigatorEventsThread::run() {
while (!stopped) {
int rc, domain;
bps_event_t *event = NULL;
rc = bps_get_event(&event, -1);
assert(rc == BPS_SUCCESS);
if (event) {
domain = bps_event_get_domain(event);
if (domain == navigator_get_domain()) {
switch (bps_event_get_code(event)) {
case NAVIGATOR_EXIT:
emit navigatorCloseEventRaised();
stopped = true;
break;
default:
break;
}
}
}
}
}
Unfortunatelly this blocks at the bps_get_event line. Why? Because there are no events coming if you don't create a bps screen also 
Right?
Next step was to replace the QApplication event filter with my own:
bool myEventFilter(void *message, long *result) {
return false;
}
int main(int argc, char *argv[]) {
QCoreApplication::addLibraryPath("app/native/lib")
But myEventFilter is never called. Why? I'm guessing because the event filter function set here is called for all messages received by all threads meant for all Qt objects. It is not called for messages that are not meant for Qt objects. Or why else?
Another way was to replace the event filter function for the QAbstractEventDispatcher:
bool myEventFilter(void *message) {
return false;
}
int main(int argc, char *argv[]) {
QCoreApplication::addLibraryPath("app/native/lib")
This was better. I got myEventFilter called on swipe down and on orientation changes. But not for application getting active/inactive. And also, to what should I cast the void *message in order to see what's actually in the message?
Is there another way, a better one, to somehow get the navigator events and add them to the Qt event loop? Or is there another solution for this problem?
Thanks & best regards,
Dumi.
[quote]Back again! And with a serious problem I've been trying to overcome in the last hours. The Application Example saves the size of its window when receiving the close event. Unfortunately this happens only when selecting File->Exit. When closing the application in the BlackBerry way the close event is not raised. And that's because that event is the navigator exit event.[/quote]
I have not had a problem with my settings gettign stored using the blackberry close method (dragging up and clicking X). For Qt c++ widget apps I call my settings function from the destructor. For qml apps I call the settings function from the main page in Component.onDestruction: {}.
This works fine, however I believe using the qcloseEvent is the proper method for widget apps.
https://qt-project.org/doc/qt-4.8/qwidget.html#clo
I am just a rookie so perhaps that is not what your looking for!
Cheers,
Jon
