Mobile and Embedded

To continue on the idea of chetankjain, a QTextEdit holds a QTextDocument and that one can have its wrapping mode set to much more complicated modes than a QLabel. One of them is QTextOption::WrapAnywhere which seems to be what you want.

As far as I know you can just use them as keys; just a special keyboard. So listen to key events and handle them. There should be appropriate enum values in the Qt::Key enum, but you can just try by printing the int value of the key in the key event.

Hi, yes by "soft floats" I was referring to a floating point library that emulates floating point operations as function calls in software instead of using the hardware co-processor. You can still use "double" on the 5230, but they will be slower than using floats. They will be additionally (and far more noticeably) slower if you use soft floats instead of hard floats. If the code uses double on Windows, then you should continue using double on Symbian, otherwise you could get different results. For this reason, qreal might not be suitable for you. Qt apps are native apps (as opposed to apps that run in a VM such as Java) so you will inevitably have different binaries for Windows and Symbian. For Windows, you probably don't need to tweak your compiler options to get the best floating point performance (I could be wrong though), but for Symbian you will have to specify in your .pro file that you want to use hardware floating points (VFP2). Like I said before I know this is supported by RVCT, but I'm not sure about GCCE which is the default compiler if you are using the Nokia Qt SDK.

Hello Rahul, Symbian has many servers. One is the "messaging server":http://developer.symbian.org/main/documentation/reference/s3/pdk/GUID-DD27A452-8B0F-5C6D-A2E6-FC21145468B6.html. "Here":http://developer.symbian.org/wiki/index.php/Handle_Incoming_SMS_Messages is an example of how to handle incoming text messages. -hth john

Hello, Others have cover the layout, the new "Sensor API":http://doc.qt.nokia.com/qtmobility-1.0/sensors-api.html from the Qt Mobility project may be of interest too. In addition to QOrientationSensor, it has QAccelerometer. -jk

Thenks. Wright there.

Looks like the linker can't find the Multimedia library. Are you on Linux? If so, have you set the environment variable LD_LIBRARY_PATH to point to the qt-mobility/lib folder? On Windows, the PATH variable needs to be extended. More info here: http://doc.qt.nokia.com/qtmobility-1.0-tp/installation.html#environment-variables

Excellent. I was hoping it would be like that. Thanks for all the info. You trolls are the greatest.

I think the closest you can come to this in Qt API is using QWidget::lower() on the top level window. That will send the underlying window to the back of the window tree and should also do the same for your window group. Hide simply hides the currently active window without changing the Z-order of anything which is why your softkeys are still visible (they are not really tied to the window). As for removing your application from the task list popup (officially called Fast Swap Window in Symbian), there is no API in Qt to do this currently so you have to do it using native Symbian code. Something like the following would probably work: @ CCoeEnv *env = CCoeEnv::Static(); CApaWindowGroupName *wgName = CApaWindowGroupName::NewLC(env->WsSession()); wgName->SetHidden(ETrue); @ You can probably find more examples on Forum Nokia.

Thanks very much. The signal/slot resolve my problem.

Looks like you don't have path to mingw in your env. Add to PATH variable path FOLDER_WITH_NOKIA_QT_SDK\mingw\bin and I think it will help you.

Yes, Service Framework will automatically start services in the background as required. The lifetime of the service is determined by the service and control is left up to the service writer.

Hi cheng, Currently, there is no standard contact picker provided in Qt Mobility. We're currently looking at whether we could provide a standard QContactAction which could provide such functionality on various platforms, but at this stage we haven't determined whether it's feasible or not. As for the image picker, I'm not the right person to answer; I hope someone else can help you there. Cheers, Chris.

Hi, well, I don't know if I've understood your problem clearly, but ... can you set a worker thread internal flag that means "it's time to get out", and send a "fake" signal to the worker thread before exiting? In this case, the worker thread can test such variable before starting, and, if it's true, it will go out in a clean way. Antonio

Thanks! That was helpful :) Will try this stuff out soon. I don't actually have a NEON compatible hardware right now to test but at least now I know where to search for more info. Thanks again!

[quote]Do you call QCamera::start() after QCamera::setCaptureMode? If you do there should be a bug in the backend implementation. [/quote] Yes. I didn’t have error logging on earlier but the errors I get now are, in order of appearance: Could not get/set settings from/on resource. Could not get/set settings from/on resource. Could not negotiate format I also get this in the Camera example application when I click on the Video tab. Edit: It's worth mentioning that trying to record video in Cheese just locks the application. [quote] Currently there are two gstreamer camera backends on linux: the camerabin based one (you have to install gst-plugins-bad and gst-photography, this backend is used on N900), and the mediacapture backend which builds capture pipeline itself. The advanced camera controls like QCameraExposureControl require gst-photography and are available only in the camerabin case. Could you try to install gst-photography and reconfigure/rebuild qtmobility? But I don't expect QCameraExposureControl to be very useful in your case, since v4l2src doesn't support the photography API for webcams yet. Those controls are much more useful on mobile devices, where camera module/driver provides much more control. [/quote] Is gst-photography its own package or is it part of gst-plugins-bad? I couldn’t find the package, but I found some files in the MeeGo Multimedia git repo that seem to indicate that it’s part of gst-plugins-bad. I installed gst-plugins-bad, though I suspect the version isn’t recent enough (0.10.14ubuntu1.1). If I could successfully set up a Meego chroot with Qt Mobility and camera working, I’d be happy to work there but so far I haven’t managed to get my app working. An odd thing is that when I was working against Qt Mobility 1.0.0beta1, I could get some camera settings like Focus Mode, though only AutoFocus was available and the webcam in reality only has manual focus. Thanks, Fredrik