QML and Qt Quick

Yes, it is all perfectly possible.

Qt Quick 1 with built-in elements

The two links above doesn't work. Can anyone tell me how to solve exactly this problem? I can't connect a signal in a delegate to a slot in my C++ code...

I re-install QT5 from .run file of QT official site, it is Ok now, thanks.

passing

http://qt-project.org/doc/qt-5.0/qtquick/qtquick-qmltypereference.html this link is good. And search anything in the top-right search box, I feel it useful.

Actually, an interesting idea is to remove the keyboard's specific implementation of their keyboard delegate and place it into a different file, then the properties will be correctly inherited: @ // library land // Bluekey.qml KeyboardButton { text: value; value: key shiftValue: key style: keyboard.style; width: buttonWidth; height: buttonHeight; onClicked: keyboardCLButtonClicked(text); buttonCLStyle: styleCLButton; shiftTextFontSize: keyboard.shiftTextFontSize; shiftTextFontFamily: keyboard.shiftTextFontFamily; shiftTextFontWeight: keyboard.shiftTextFontWeight; shiftTextColor: keyboard.shiftTextColor } // bluekeyboard.qml Rectangle { id: keyboard // bunch of properties .... property Component keyboardDelegate: Bluekey { } Repeater { model: myModel Loader { property string key: myModel.get(index).key sourceComponent: keyboardDelegate } } } // user land //main.qml Rectangle { property Component buttonDelegate: Bluekey { color: key == "E" ? "red" : "blue" } Keyboard { keyboardDelegate: buttonDelegate } } @ Any feedback on this? Thanks for the suggestions Jens!

Thanks a lot. That answers my question.

Quick look seems like you have given me an answer, I will get on with the coding. BIG thanks

The property types which are provided by QtQuick are listed at http://doc-snapshot.qt-project.org/qt5-stable/qtquick/qtquick-qmltypereference.html#basic-types however not all of them have conversions to uniforms/varyings in ShaderEffect. Matrix3x3 doesn't exist at all. vector2d, vector3d, vector4d, quaternion and matrix4x4 should all have conversions. Cheers, Chris.

Oh, Qt53Dd.dll and Qt53DQuickd.dll are in my $QTDIR\bin. :)

Hi, This might actually be a bug, if the relative URL is being resolved wrongly based on the base URL of the component. I assume that "file:///path/to/app/myapp-build-042394-Release/scripts/x.js" is the incorrect path, and that your project does not install the file there? On the other hand, if that is the correct path (ie, the resolution is correct) and the project does install the file there (so it exists) but it still can't access it, then I'm not sure what could be happening. Cheers, Chris.

Everyone who is interesting in this thread should watch "QTBUG-30305":https://bugreports.qt-project.org/browse/QTBUG-30305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel .

It looks like the above two posts are on the same (QML) issue, so I merged the separate topics you created and moved it to the Quick forum.

Ah wait, so this component is loaded into a Loader! That's probably an overkill (it would work without the loader just fine). In order to get to the belly of a Loader, you need to acces it through item property. Here's a snippet: @ Loader { id: loader source: "whatever.qml" } // somewhere else in code (JS. C++ would work, too): loader.item.color = "#12ff87"; @ Hope I finally understand your code now :P

Thanks. So It's one more reason to prt my project to Qt5.

Thanks for your advices. However, I have a project to do, the faster the better, and moreover, I have a whole bunch of plugins READY, but NOT_QML. So I have to "qmlize" them all the way to make available the objects, provided by plugins, to game designers, who will actually work in QML, to bring a game rules into action. I do not use QtQuick because I make not-a-casual game. It is better to see I guess: "Video":http://www.youtube.com/watch?v=wySHVtY_3cw. As the game is going to be CPU intensive (later on), I need to apply threading. This is why I want each plugin to run its objects in separate thread. And I have it now, with my non-qml plugins, but those qml plugin interfaces are found to be far more attractive for game design. I registered my QObject from App (not from plugin) and it works just fine. That will do. For now only question #2 is yet unresolved, I am going to prepare plugin exporting and then I go directly into question2 issues for my own investigation. All in all I hope for an elegant solution and do want to discuss different approaches here.