QML and Qt Quick

i thank you! =)

I realized that I have set openvg as graphics system in my main.cpp and that was causing above issue. "QApplication::setGraphicsSystem("openvg");" After removing above line from main.cpp. My application is working fine now.

And here I thought it was some heavy C++ issue that I wouldn't understand. :o) It was right there in front of me!! Thanks both of you for your help!

I have successfully used QString locale = QLocale::system().name() to translate a mobile application for harmattan, n950 with latest firmware. Used meego 1.2 harmattan api and it returned it_IT with my current settings.

Hi, I have the same question, please any help? How I can set the user agent for this example: "http://doc.qt.nokia.com/latest/demos-declarative-webbrowser.html":http://doc.qt.nokia.com/latest/demos-declarative-webbrowser.html Thank you

Thank you a lot! Really helpfull :)

[quote author="spode" date="1317321543"]@ void prima::nuovo() { seconda s; s.show(); close(); here: goto here; } @ the window stops working...[/quote] Oh, that's just so wrong in so many ways... see above. But let's step through the code... @ seconda s; // This creates the object s.show(); // This shows it. It DOES NOT BLOCK AND WAIT FOR THE WIDGET TO CLOSE close(); // This closes the window immediately. @ Here's an exercise. What do you think the @ here: goto here; @ code does? (Hint... tight, infinite loop)

[quote author="jr_jags" date="1317314928"]yup, anu b ung name ng game nio? [/quote] What is the meaning of this? Is it Qt related? If it's just about learning to know each other you could send a mail using the profile page ;) Edit: Deleted the referenced post, per the poster's request; mlong

May be you need to look at XmlRole and XmlModels http://doc.qt.nokia.com/latest/qml-xmlrole.html check out this project: http://projects.developer.nokia.com/QuickFlickr/browser it handles some XML in QML

Ok, so I solved this by implementing a slot. One thing QtQuick should think about is to provide a consistent API set for all the models.

[quote author="Andre" date="1317273695"]This is about QML? In that case, I am moving the topic. It was not appearant that you were talking about that QML at all earlier, so in that context, Vass's answer is very relevant. I think that even from QML, you will need to use QProcess through C++/QML integration, but I am not sure. [/quote] Oh, my bad. In that case, thanks. I'll try to use QProcess.

PathView.moving doesn't work properly, elements don't move smoothly when you do like this Image.smooth: !PathView.moving PathView.flicking is not even possible to use, because elements are moved programmatically due to call to PathView.incrementCurrentIndex().

Oh, I see. Another thing I've learned. I still don't think I have got everything clear out of the loop of docs PageStackWindow - PageStack - Page - ToolBar - ToolBarLayout - tools... The principle and outcome is simple, yet at this point the docs themselves are more complex than needed. Looking forward to see a simplifications as soon as the com.nokia.meego stuff gets assimilated in Qt Quick components upstream. Anyway, not an excuse for me. I'm looking again at the examples provided at http://harmattan-dev.nokia.com/docs/library/html/qt-components/qt-components-meego-menu.html and they keep tool and menu separate.

Ok, thank you very much for your help and for getting me on the right track :)

yup, the mainloader.source will move you to another qml, and at the same time i want to implement the other functions on my mousearea onclicked, I tried moving all these commands to a javascript function but still, i experienced crash on my simulator,

I agree, I have used this method somewhere in an application with good results. Not rememebr now where ... But I need to reuse this in a application I am working on so I can provide and example further if needed.

Hi, The target property is defined for the instances of the component, rather than the component itself, so it needs to be set on the objects returned from createObject: @var obj = component.createObject(parent) obj.target = targetItem @ If you are using QtQuick 1.1 you can also do something like the following (which is faster and should potentially generate fewer warnings): @var obj = component.createObject(parent, { target: targetItem }) Regards, Michael