Cannot you upload the image to imagebin or something like that? It should not look different if the screen resolution and text are the same in the simulator and device.
The layout you set should make the buttons remain at the left of the screen with their preferred size. You could also try removing the linear layout and using only the anchor one to try and see if it behaves differently. I mean, by anchoring each of the buttons to the left of the layout. Then one on top of the other, and finally glueing their right side together.
Sorry, I do not understand your code at all.
I am pretty sure you are not saving anything into the file. Check the generated file and make sure that the data you expect is there.
QVariant::toString() is not meant to serialize data but to convert simple data into strings when possible. It will most likely fail with complex data found in a typical QVariantMap and return a empty string.
What type is "contacts"? I guess a QVariantMap or something... You are generating a key "filename" there and put some data into that (not into any file).
You do not read any data from the file in the open_button_clicked method. So even if you had managed to put data into a file you will not be able to restore it.
No idea what you want to do with the iterator... There is no loop, so you are not iterating over the contacts data. You find the position of the element you care about, then move to the next element. If you are then at the end of the data structure you move to the first element... yeap, that works, but only if there is exactly one element in your structure.
I would suggest doing the following:
remove "contacts". I do not see why that is needed.
Print content and data variables in save_button_clicked. Make sure it is what you expect. Fix the code till it does.
Open a file, write a static string into it, close it again. Check that the file is really created and contains the string you wrote into it.
Replace the static string with the data. Check that the file is still created and contains the expected data. Fix the code till it does.
Only when all this works I would continue with the open_button_clicked method, using a similar approach. No, I will not provide code: Coming up with this code is your job, not mine:-)
Thanks for your reply. You are right. Sorry for the question but this environment is new for me.
I clicked on connectivity button and appears the label "Connecting...". After while disappears and nothings is shown.
I will try your solution.
We are not in a feature freeze, so I can not say what will be in the next version of creator, even less so what will be documented;-).
I just wanted to point out that we are improving the deployment area of functionality. A wiki page would be helpful for us for the following reasons:
It documents where you run into trouble, providing valuable feedback on what to improve.
It could get integrated with the offical documentation (if the authors are OK with it).
Both would be good I think:-)
For anyone else who is similarly intellectually challenged:
The Qt download is from http://qt.nokia.com/downloads. The required downloads are hidden behind the LGPL tab, so click on this tab or you won't find them (took me ages ;o( )
If you already have a Visual Studio installation then you can download "Qt libraries 4.6.3 for Windows (VS 2008, 194 MB)"
Or if like me you don't, and also want a minimal implementation, download "Qt libraries 4.6.3 for Windows (minGW 4.4, 280 MB)"
Other instructions as above
QGalleryRemoveRequest affects the whole operating system. There's no way to reverse the operation from within the document gallery API. If the document is in the crawl path of the indexer it may get added back automatically (which admittedly isn't ideal) if the indexer doesn't blacklist removed files. Otherwise if a document was inserted by other means it could be restored by repeating that process.
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.
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.
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.
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:
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());
You can probably find more examples on Forum Nokia.
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.
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.
[quote]Do you call QCamera::start() after QCamera::setCaptureMode?
If you do there should be a bug in the backend implementation.
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.
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.
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.
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:
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.