QML and Qt Quick

@LeLev Many thanks!

@jeremy_k you're right, @Witzgy you may get a much faster translation happening when you do the old way of translating / updating translatable strings, with the empty string update: https://wiki.qt.io/How_to_do_dynamic_translation_in_QML also, it would probably help if you do not load all QML components on startup. Dynamically created pages/components fetch the correct language string automatically, and you only need to update those, that are currently created. Thats why I have a StackView as root component, where I keep the stack size to a minimum (always pop before push)

Hi, Boot2Qt being a commercial offering, you should contact the Qt Company directly.

@Elg1 I don't think anyone/the OP is around any longer to answer from a thread from 5 years ago! Suggest you open your own new thread question.

@bogong said in Qt 5.15 Depricated: QML Connections: Implicitly defined onFoo properties in Connections are deprecated.: (...) Connections { target: oTarget; function onSignal () { mYourFunction(); } } Hello, Maybe I'm wrong but in Qt Design Studio: Functions are not supported in QtQuick UI form. (M222) ... I don't find a way to use it correctly (I use old form with deprecation warning)

Thank you, you are right!!! I donť know why, but i tried QQmlProperty.... QVariantMap didn't think of that Tnank you!

@Elg1 If you use lambdas then you can pass the SpinBox instance as parameter.

@mzimmers said in updating elements in a repeater?: Well, bless my buttons...that works! Nice :) @mzimmers said in updating elements in a repeater?: But why is bottleList() declared as returning a QVariant, and not a QVariantList? I don't have a technical explanation for that really, im used to do that since i saw it somewhere in the docs. But i guess you could return a QVariantList directly. It will be converted to javascript array as explained here https://doc.qt.io/qt-5/qtqml-cppintegration-data.html

@Balaji-Sivakumar Sure, I think those are options you get to make a better rendering on what you are doing currently, if you need further explanation maybe you can check the following documentation: RenderTarget: https://doc.qt.io/qt-5/qml-qtquick-canvas.html#renderTarget-prop RenderStrategy: https://doc.qt.io/qt-5/qml-qtquick-canvas.html#renderStrategy-prop

The OpacityMask is quite a bit more powerful: // masking objects to unique shapes Rectangle { id: mask width: output.width height: output.height color: "transparent" Rectangle { id: corner_mask property real size: parent.width * 0.1 width: size*2 height: size*2 radius: size*2 color: "red" visible: false } Rectangle { id: corner_rect width: corner_mask.width height: corner_mask.height visible: false } ShaderEffectSource { id: shader_effect_mask sourceItem: corner_mask sourceRect: Qt.rect(0,0,corner_mask.width/2,corner_mask.height/2) } OpacityMask { anchors.left: parent.left anchors.top: parent.top width: corner_mask.width/2 height: corner_mask.height/2 maskSource: shader_effect_mask source: corner_rect invert: true } OpacityMask { anchors.right: parent.right anchors.top: parent.top width: corner_mask.width/2 height: corner_mask.height/2 rotation: 90 maskSource: shader_effect_mask source: corner_rect invert: true } Text { width: output.width text: "The OP is from 2018" font.pixelSize: 100 font.bold: true wrapMode: Text.WordWrap horizontalAlignment: Text.AlignHCenter anchors.centerIn: parent } visible: false } // the maskee Rectangle { id: output width: 512 height: 256 color: "steelblue" visible: false } // just do it! OpacityMask { source: output maskSource: mask width: output.width height: output.height invert: true }

Please let me know if there are any way available to access QtMultimedia from sub module's qml file.

@mzimmers said in "underlaying" a rectangle: I do think my problem comes from using Column instead of ColumnLayout i'm not saying that at all... i don't know where your problems come from since you don't show the code :) the only relevant part of my example is the blue and pink rectangles with their parent, dont pay attention to my ColumnLayout please

QSGGeometry * geo2 = new QSGGeometry(QSGGeometry::defaultAttributes_Point2D(), 4); // create geometry The crash is due to the 2D point which is not enough to hold the texture, the call with QSGGeometry::defaultAttributes_TexturedPoint2D() (QSGGeometry::TexturedPoint2D) will solve the issue.

For anyone with the same issue: The cause here seems to be name shadowing. See https://forum.qt.io/topic/74969/qml-how-to-access-context-property-if-its-name-is-shadowed-by-a-component-local-property

@Mammamia Thank you! This is exactly what I was missing.

@aatwo You can file a bug in Qt bug tracker