Mobile and Embedded

Great! nice to "hear" you solved your issue :-)

Hi John, Just to be sure, you reinstalled TRK after the firmware upgrade, right? To produce a test case, try to reproduce the problem with a small code and describe the steps you do until the debugger error happens. Oh, yeah, if gdb says any error message, it can be useful. Providing a sis package of this small test case is a good idea too. If you have any doubt about your testcase, post it here. When we identify if it is a bug and which part is causing it, you'll be able to write a better bug report :-)

My apologies, I didn't even notice that this was on our internal server. I'll mention this to the guys behind this and see if they can fix this.

The QSplashScreen takes in a QPixmap. You can scale the pixmap to whatever resolution you want first and then assign to splash screen. Just tried and works fine ... @ QPixmap pixmap("c:/design.jpg"); QSplashScreen splash(pixmap.scaled(1000,1000)); // the orig pixmap was 640x360 and shows up in that size if I don't scale splash.show(); @

Yes, you are right that notification popup is the UI element - different on different platforms. Behind this UI elements should stay some notification back-end (daemon service or something) which receives notification requests from client applications and delivers them to system ui notifications widgets. I thought that some common API for this back-end for all platforms can be useful and allows the developers to write more portable applications. BR, Pawel

hi sriky27, can u convert the url to a link?

Hi, I think it should be possible to write a plugin for Phonebook in symbian cplusplus I have to double check this, I remember there was phonebook plugin extension possibility but not with the Qtplugin add-ins as per now. In Symbian v 4 if i have understood it right the complete Avkon component (Current Symbian UI framework) is being re written in Orbit UI (Qt based Ui framework). May be it might be possible then.

sriky27, enclosed the code with @ tag

Hello, Native Symbian development is always available to you. The telephony libraries there are quite rich. It is possible to write an application which combines Qt for most everything and use Symbian for the telephony stuff. Here is an article talking about "using Qt together with Native Symbian C++":http://developer.symbian.org/wiki/index.php/Apps:Using_Qt_and_Symbian_C++_Together. -jk

[quote author="maxvanceffer" date="1286542257"]I made this using window method setWindowFlags(Qt::WindowFullScreen); but this working not properly, maybe in new QtMobility release trolls fixed this.[/quote] How is QtMobility going to fix this. AFAIK its not for any UI widgets or controls.

Hi Antonio, Thanks, it works.

Thanks you! I did that. It's OK. Thanks a lot!

Well, it works already for read, and there's example working. i ḿ in the stage of implementing User object and then the rest of Objects This is more a cur and paste tedious work, but need be done. The single QFacebookGraph class can be used directly too. Auth is not doing by the library, since Facebook terms not allow you doing directly instead of access their web sign on, so second example implements an local auth using web touch page.

Check for capabilities.You need readDeviceData capability to read messages. "Capabilities":http://developer.symbian.org/wiki/index.php/Capabilities_(Symbian_Signed)

Thanks you very much, I understand!!

The last thing you can tweak if you have a small amount of memory on your system is the BLOCK_SIZE allocated by the collector, the default size is 256K if QT is not compiled for symbian nor wince, which can be much more than your scripts need.

Thanks for the information. [quote author="chriadam" date="1286339315"]As for building for and deploying to the Nokia Qt SDK Simulator, I’m not entirely certain whether that’s possible with Qt Mobility 1.1-beta at the moment (the current version of the SDK supports Mobility 1.0.2 I believe; I’m not certain what’s required to upgrade the SDK mobility version from 1.0.2 to 1.1.0-beta2.[/quote] Ok - I think this was what I was getting hung up on. Since the Nokia Qt SDK comes with Qt Simulator and Symbian / Meego targets, I made an assumption that the Qt Mobility SDK also supports these targets. I think it would have been better to state on the installation page that Qt Simulator is not supported. I don't have a seperate Symbian SDK installed - can the Symbian target that comes with the Nokia Qt SDK be used, or do I need to somehow install and configure a seperate Symbian^3 SDK?

oooold topic, but it's nice to put references for the ones coming from search engines. Instructions to install PySide Mobility (python bidings for Qt Mobility) on Maemo 5: "http://developer.qt.nokia.com/wiki/PySideBinariesMaemo":http://developer.qt.nokia.com/wiki/PySideBinariesMaemo