QML and Qt Quick

Hello everybody,

I'm overlucky: I found the error for myself (-:

The correct code line is now:

emit dataChanged(index(0),index(nparticles-1));

instead of

emit dataChanged(index(0),index(nparticles));

Now I can start working!

Thanks to all!

Tobias

Changing the name fixed the runtime error, thank you. However, qmlls still complains about the import ("Warnings occured while importing...") and says "Unqualified access". Can you tell me why?

In my real-life code I want to instantiate an instance of a class in c++ and hand it over to QML without setting it as a context property, hence the call to qmlRegisterSingletonInstance.

SOLVED thanks to a previous forum post regarding using MultiEffect on Image{} type component

All that's required is to set VectorImage's visible to false, since the compositor seems to be double rendering, I suppose, creating the unwanted outline of the SVG

Thanks to 6.5 article: https://forum.qt.io/topic/144070/qt6-color-svg-using-multieffect/3
and member: https://forum.qt.io/user/mzimmers

New graphics:
3f636858-1079-499b-9803-afcd8b926c3c-image.png

WORKING CODE:

Item { id: root color: <input from higher level> source: <input from higher> VectorImage { id: mySVG ~~~~ same lines from above ~~~~~ visible: false <======== DONT FORGET THIS } MultiEffect { id: colorOverlay source: mySVG anchors.fill: mySVG colorization: 1.0 // opacity equivalent colorizationColor: root.color } }

@SimpleY i ve got same problem as your, try to go to preferences->Qt Quick->QML/JS editing-> QML Language server and remove tick on Tun on (leave all unchecked)

it worked for me.

QScrollArea has a method ensureWidgetVisible() which seems to be missing from Flickable. StackOverflow had a discussion on this: https://stackoverflow.com/questions/45946637/how-to-make-flickable-ensure-the-visibility-of-an-item-inside-of-it. (I'm not a user of QML, but this might provide a different way of tackling the problem.)

@johngod This is a great reference. I will check the code and compare what I am doing wrrong here.
Thank you so much.

It isn't that TextArea isn't able to "handle" Images; you can indeed place images within a TextArea and control their location. The problem is, your image is embedded in the text property of the TextArea. I've never seen this done before, but I think you'd have to use HTML/CSS constructs within the <img> in order to do anything (and I'm not sure this will work).

Turns out it wasn't me doing something wrong. It was a Qt bug: https://bugreports.qt.io/browse/QTCREATORBUG-31949

@GrecKo Thank you very much! You really help me solve this problem!

https://bugreports.qt.io/browse/QTCREATORBUG-31897

@Mesrine I tried your example. See what happens if you press the tab key after the dialog appears. Not working quite correctly.

@dheerendra said in HorizontalHeaderView ColumnWidthProvider confusion:

ColumnWidthProvider This property can hold a function that returns the column width for each column in the model
Based on the above documentation, I did the following:
[...]
columnWidthProvider: root.columnWidth(column)

When you are doing this you are not passing a function to the columnWidthProvider. This code instead tries to execute the root.colummWidth function by passing column as the parameter (most likely undefined here and pass the return value to columnWidthProvider. Did this produces a warning?

What you wanted to do is:
columnWidthProvider: root.columnWidth (or what afalsa wrote).

I agree that an example or 2 in the documentation won't hurt.

Thanks @afalsa. Yes. Output is not an issue. If you specify both delegate & textRole, textRole has no impact. Delegate takes priority. If you remove the delegate, then textRole kicks in. There is no bug also. Need to docs clear about this.

Fixed by modifying arrowIcon

Rather than using Rectangle as a "page", use Page QML https://doc.qt.io/qt-6/qml-qtquick-controls-page.html and build/write your code within that page.

What's the idea behind using PathView?, just use Page.

I couldn't do much with your code, I did try, but there were too many errors and other data missing. A working code snippet often helps.

@Pl45m4 I mean qt form,i dont know this environment(english is not my native lan),yep px4 is for drones,thanks for reply

I don't know how to prevent the qml from deleting the shared pointer.
So I return a new classs to qml, it works well. Hope anyone can tell me if it corrected.

} else if(role == modeRole) { if(deviceVariable.modeModelPtr.isNull()) return QVariant(); //return QVariant::fromValue(deviceVariable.modeModelPtr.data()); return QVariant::fromValue(new ModeModel(*deviceVariable.modeModelPtr)); } }; DeviceVariables { // .... QSharedPointer<ModeModel> modeModelPtr; } class ModeModel : public QAbstractListModel { public: //.... ModeModel(const ModeModel &other) : QAbstractListModel(other.parent()) { modeList = other.modeList; } private: QList<ModeData> modeList; };

I debug the ~ModeModel() and found the qml will auto delete the new ModeModel() which I provide in the cpp.