QML and Qt Quick

Anyone can further provide update on this ?

OK, thanks for the replies. I make large applications, I will not do something great with QML, but will not be small. will have many of user interface screens, maybe 30 ~ 50. do not want heavy application. Will it consume too much CPU or Memory or will it take to start?

I don't know much about why this warning is emitted, but it happens when the (in this case, default) GLSL shader (and in this case, I assume it's a fragment shader) is compiled. We're getting well out of my area of competence, but I think that there's probably an issue with ANGLE regarding how the GLSL shader is converted to HLSL, which causes an assignment (most likely of a uniform) to a different type, causing an implicit truncation. Build your Qt with desktop openGL configuration instead of ANGLE, and you should see this go away. Cheers, Chris.

http://stackoverflow.com/questions/9153629/regex-code-for-removing-fwd-re-etc-from-email-subject Found something for the above

I have been trying to use the Qml-grid view in my code. I am on a mission to couple it with my C++ code which I have been in vain so far. I think my problem occurs when I try to generate the signal from the qml rectangle. I will definitely update you with the results once I have done with it. "super-beta-prostate.com":http://www.super-beta-prostate.com

I'm not entirely sure what you mean, so maybe my advice won't be useful. But, basically: your "QML module" will be installed to a directory (the QML import path). Your application, which imports that module, can reside wherever it likes, it just needs the correct import statement. For example, if in your application's QML file you have: @ import com.example.components 1.0 @ then the QML engine will look in $QTDIR/qml/com/example/components for the module specification file ("qmldir"). You shouldn't need to include any of the paths to anything, in the .pro/.pri files of the application itself. To answer your final question, yes it's absolutely possible to define plugins with C++ defined types - there is a section about that in the documentation. Your plugin cpp should use qmlRegisterType (and related functions) to register the C++-defined types as QML types. Cheers, Chris.

waitForFinished blocks the event loop so converterStarted and converterFinished will be called one after the other after converterProc has ended thus you won't see "Wait!". If you just want to avoid several start of the converter and keep you UI responsive, you could disable pushButton while the converter is running.

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. :)