Mobile and Embedded

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

As you have guessed, we no longer officially support Qtopia. The last released version was named Qt Extended 4.4. While you may not have found any info specifically related to your board, this is not that strange because Qt doesn't contain anything specific to a particular hardware board. Qt supports the ARM architecture you are using as well as your kernel version so that is most likely enough. Assuming that you have a working cross-compiler installed on your host PC, then the next step is to download and cross-compile Qt Embedded using the device's toolchain. I recommend starting here: "http://doc.trolltech.com/4.6/qt-embedded-crosscompiling.html":http://doc.trolltech.com/4.6/qt-embedded-crosscompiling.html Getting things like the touchscreen working may require some tinkering, but you might be able to find some code for this in the Qtopia package released by the manufacturer. It could be as simple as porting their Qt 2 based code to Qt 4.

Answer is "here":http://developer.qt.nokia.com/forums/viewthread/264/

If it is acceptable for you to open external application (not software component) than you can use QProcess. If you want to use WMP as software component than you should look for phonon plugins working with WMP.

Qt uses the native file dialog on Maemo 5 ("Maemo docs":http://maemo.org/api_refs/5.0/5.0-final/hildonfm/HildonFileChooserDialog.html), which disallows browsing anything but the home dir and the memory card. To browse the entire file tree (and risk being rejected from the Ovi store), you can use a QFileSystemModel on a QTreeView?

That was exactly it, thank you

All code is available on "gitorious.org":http://qt.gitorious.org/qt-mobility

I think that launching can be done via QProcess class, but killing them and checking RAM only via native Symbian code (or by running some system utilities via QProcess and parsing their output)

Ok thanks.

Guys, feel free to edit Wiki page here: http://developer.qt.nokia.com/wiki/OpenCV_with_Qt Add you questions and suggestions there too.

[quote author="silvansky" date="1278666566"]for now there is QT_SIMULATOR macro for source files (in the latest Nokia Qt SDK) but I don't know if there is somethong for .pro files UPD: in .pro files you can use simulator { # do something }[/quote] Thank you