My shoulders hurt.
-
-
@anderslund I mean you are using = in QML, so seems mostly "a you are doing it wrong" problem and not a QML problem. Of course if you don't share the rest of the code it's hard to evaluate what's going on.
-
@anderslund I mean you are using = in QML, so seems mostly "a you are doing it wrong" problem and not a QML problem. Of course if you don't share the rest of the code it's hard to evaluate what's going on.
@tsdgeos
Thanks. This was some event handler (onTriggered), and there was another reference to the same object in the line above that worked.It is a function, so javascript - = tends to work in such cases.
In the meantime I changed some things, and got it working, but I do sometimes run into issues like that. In this case there was no warning or hint, so I used a function to access the object, and it worked.
I believe it had to do with me using a stringlist as model, and using a proper ListModel made it go away
