QML and Qt Quick

[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

already made! the error goes on---

Thanks for the replies. I tried to figure out if there is any restriction to MultimediaKit in the opensource version but couldn't find anything about that rather than it seems to be available unter opensource license. I installed the newest QtSDK, download the Mobilty sources and compiled it but it fails at some point in the qsysteminfo_win.cpp where some includes are missing. Seems an already reported but not yet fixed bug :-( I try to dig what's going wrong using the sysinternals Process Monitor to find out where my application is looking for the MultimediaKit. It seems to look for a directory called QtMultimediaKit.1.2 with another directory qmldir inside. Those directories are not existent. @ 09:45:39,4623518 VideoTest.exe 1816 CreateFile C:\QtSDK\Simulator\QtMobility\mingw\lib\Simulator\QtMobility\mingw\lib\QtMultimediaKit.1.2\qmldir PATH NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 09:45:39,4631537 VideoTest.exe 1816 CreateFile C:\QtSDK\Desktop\Qt\4.7.4\mingw\imports\QtMultimediaKit.1.2\qmldir PATH NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 09:45:39,4635392 VideoTest.exe 1816 CreateFile C:\QtSDK\Simulator\QtMobility\mingw\lib\Simulator\QtMobility\mingw\lib\QtMultimediaKit.1\qmldir PATH NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 09:45:39,4642857 VideoTest.exe 1816 CreateFile C:\QtSDK\Desktop\Qt\4.7.4\mingw\imports\QtMultimediaKit.1\qmldir PATH NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 09:45:39,4646641 VideoTest.exe 1816 CreateFile C:\QtSDK\Simulator\QtMobility\mingw\lib\Simulator\QtMobility\mingw\lib\QtMultimediaKit\qmldir PATH NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a 09:45:39,4654133 VideoTest.exe 1816 CreateFile C:\QtSDK\Desktop\Qt\4.7.4\mingw\imports\QtMultimediaKit\qmldir PATH NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a @ But I found in the QtSDK under C:\QtSDK\Simulator\QtMobility\mingw\lib the QtMultimediaKit1.dll and libQtMultimediaKit1.a. So it seems that the Multimediakit is there but not accessible for my Application. So I try to set the PATH to that directory but it doesn't help. Any other ideas what is wrong in my setup? Thanks for your help

Hi borut123, I saw you reimplement "get" function of model in c++ header file. Does its return value YourObject is your model's pointer? Should it be the pointer of item which model stored, not model's ?

Stupid boy! :) Just discovered that it seems to only work to return @QList<QObject*>@ and not QObject derived types. 4.7.1 let me do nothing with it and because of 4.7.4 crashing I read one or two (hundred ;) ) times again through the docs... But now it works flawlessly! :) PS: The problem that @QObject::findChildren<SomeObject*>()@ does not find all children in the subtree remains, any ideas? Shouldn't they be there if I set their parent through @QDeclarativeItem::setParentItem()@ or did I misunderstood something conceptionally?

[quote author="TobbY" date="1316635942"]sorry its not program, its just an prototype to ask question[/quote] An actual code snippet would probably be more helpful in determining what may be going wrong. Often the problem is in the details that one takes for granted.