Mobile and Embedded

Small update: We put the patches online (same URL as the binaries). The manufacturer of the WeTab is also looking into it.

No, you should explicitly download Qt 4.7.0 and install it.

Have you debugged and checked if the map is being fetched

yes it did, but that was, when running the app through the simulator. I will test the availability of postgres driver from inside a mobile device..

[quote author="rohanpm" date="1288016351"] from within the app, use QProcess::startDetached to start another instance of the app, then exit (the parent) immediately[/quote] I would suggest an improvement for that: fork. in parent: terminate the app. in child: make a delay, so your app gets enough time to terminate and use QProcess as offered above.

checklib: error: library \Nokia\devices\Nokia_Symbian3_SDK_v0.9\epoc32\release\ARMV5\urel\QtUiTools.lib is incompatible with standard C++.

I will be very happy if you add "Kannada":http://en.wikipedia.org/wiki/Kannada also to the supported list.

Oh yeah, after last week's announcement, things changed :-)

i think, that the app gets to low storeage for use from the device. so it cant show all these icons at the same time, but thats just an assume.

This looks like a great place to use a "QSignalMapper":http://doc.trolltech.com/4.7/qsignalmapper.html.

[quote author="QtK" date="1287741731"]Thank you, I was looking for something like QLayout::removeWidget()[/quote] you could alternatively use QLayout::removeItem(), and then add them back with QLayout::addItem().. you probably already also know this by now :)

well i have tried it, i have two objects which take about 2 sec for constructing each of them, i wanted improve on it, so that the objects gets constructed in parallel. -Sriky

Maybe "camera API":http://doc.qt.nokia.com/qtmobility-1.1.0-beta2/qcameraexposure.html#FlashMode-enum could help you

[quote author="Aleksei Mikhailichenko" date="1287746081"]Did you tried setContextProperty? [/quote] Yes. Just tested again here, working nicely. This kind of error used to happen when the binary was created with a different version than the one installed on N900, due to internal changes in QtDeclarative during the development of Qt 4.7.

So even in future releases its not expected.

Maybe it's bug, can you write test application?