QML and Qt Quick

@St-Stanislav readParameters() and writeParameters(). Are they signals or methods ? If they're signals, you'd better create a signal in QML, and connect it to the C++ side It's explained here: Connecting to QML signals If you plan to use ParameterID data type in QML side, don't forget to register it properly in the C++ side. K.

@fcarney Yes, I thought about using an animation sequence...it can work. As I'm using a Behavior animation type, I 've been using the following: Behavior on width { SpringAnimation { spring: 4; damping: 0.4 onRunningChanged: myAnimFinished = (running === false) } } I'll evaluate both solutions in terms of performance.

The solution I adopted in the end is to create dinamically a single LineSeries object for every line color, and that works pretty well even if I have to create 40-50 lineSeries objects. I'm not pretty sure that the way I'm adding LineSeries is the best (I don't like the approach I used, but at the moment I don't see other possibilities). When I need to draw the lines what I do is: send a signal from c++ to qml that we need to draw new lines, with the number of lines to be drawn. with a Connections object I intercept the signal in qml and inside a for I create a new LineSeries element using chartView.CreateSeries(). Then I pass the series back to c++, with the number of the LineSeries created, so that I know which points I have to assign the that LineSeries object. I know that is not a clean approach, if somebody has any hints please tell me.

I made little changes to my code so that: In the settingsPage.qml file, I have this inside of onToggled: backend.switchValue = toggled In the homePage.qml file, I have this inside one of the rectangles I've created: visible: backend.switchValue() Lastly, in main.py file: customTitleBar = Signal(bool) @Slot() def switchValue(self): return customTitleBar.isToggled What am I doing wrong?

Either buy the PDF component separate or license the commercial version of Qt. It is not included in the open source version.

Update: by process of elimination, I traced the cause to my use of ColumnLayout. Changing topic title accordingly. EDIT: So, it appears that the missing ingredient was a Layout.preferredWidth: Label { Layout.alignment: Qt.AlignHCenter text: changeConsumablesViewModel.posterModalSubHeading width: parent.width * 0.9 Layout.preferredWidth: width fontSizeMode: Text.Fit minimumPixelSize: 18 font.pixelSize: Theme.plateLabelLargeFont.pixelSize wrapMode: Text.Wrap } produces this: [image: f402a6ef-db23-40f7-9c29-c52749ba903f.PNG] I didn't realize that I needed to apply Layout properties to the individual elements of a Layout; but evidently I did.

Hi, and welcome! @edfasefwfawd said in How can I enable the native Windows style?: Some of the Qt 6 material talks about native desktop styles. I'd like to use the Windows one. How can I enable it? If I'm not mistaken, it's already enabled by default. Just create a basic Qt Quick project and build it with both Qt 5 and Qt 6: import QtQuick.Window 2.15 import QtQuick.Controls 2.5 Window { width: 640 height: 480 visible: true Button { text: "Hello" } } On Windows 10, when using Qt 5, the button is large, flat, and always gray. However, when using Qt 6, the button is smaller with a blue-ish hover effect, just like native Windows buttons.

This might help too. It has this described: Image { source: encodeURIComponent("/tmp/test#1.png") }

@fcarney Thanks. It solves my issue !

@fcarney said in version number for QML imports: But it can affect properties available in objects: Yes, and OP is aware of it: I have tended to use the lowest import version number I can, so I keep at the most minimum QML "API" for the features I need So in my answer I focused on other stuff. Of course, you should not lower the number so much that you start loosing features you need :-)

@kkoehne ah, after reading your reply, the error message makes (a little) more sense. That's not a great error message though...both it and the docs section talking about the deprecation could use some rewording, IMO.

@penpen said in Resizing of QQuickView very slow and flickering: I've found some solution that is not perfect but muche better than default behavior QSurfaceFormat format; format.setSwapInterval(0); format.setRenderableType(QSurfaceFormat::OpenGL); view.setFormat(format); Ho, i have the same problem and the same GPU: 1060 6gb. Some solution?

Another route is creating a custom image provider. With that you choose how to interpret the end of the url. The data will be provided to the Image item via a handler.