@esvo
[PROBLEM SOLVED]
Turns out its a problem that is independent of windeployqt or qtcharts. Will be logging my findings here in case anyone else comes across this specific-ish issue as well. (Or if anyone has other insights)

The qml files with the charts being loaded in use singletons. I registered these singletons in the c++ main. When I registered the singletons I have the code looking into the working directory for the singleton qml files using the QDir::currentPath() function.

The folder including all the singletons must be included in the same folder as the exe for the app to have access to these files. Dropping the folder with the singleton qml files into the same folder as the exe fixes the problem.

@JonB

But you talk about "The purpose is to have different lines/coloring for each line". That implies to me you do want multiple, separate line series, each with their own points and color?

Yes.

In that case you do want new QLineSeries created each time round the loop, so you end up with 5 lines (and get rid of the wasted one outside the loop).

Okay, thank you. I did this and with a little bit of refactoring I got it to work as expected. Appreciate the assistance!

"append" causes a redraw. There is no way to disable the redraw that I can find. The QML api for charts is kinda crappy for adding data points. Which is why I had to use "replace" in C++. I have done thousands of points this way and it doesn't cause delays in the UI interface.

@J-Hilk Thank you for answering the question.

Take a look at VXYModelMapper . It lets you create series from a QAbstractTableModel with not all the glue code you did here.

@JonB
Thanks for pointing that out, I completely missed it.
I'll go with PySide2 until more features are released in Qt6 like you mentioned.

Thanks again.

Wating bugfix
https://bugreports.qt.io/browse/QTBUG-85053

so for now I use this which seems to work...

xAxis->setRange(0,dat.size()); yAxis->setRange(*std::min_element(dat.constBegin(),dat.constEnd()),*std::max_element(dat.constBegin(),dat.constEnd()));

@mrjj thank you :)

@Gojir4 yeah, that's more or less how I used the Component.onCompleted

@lopeztel said in Property of object is not a function:

This is what happens when you spend hours staring at the screen ...

Sometimes when you have had too much to think you need a break and coffee.

I'm not sure how this happened to the previous two question askers, but for me the solution was quite simple. Qt works just fine at displaying the plot axis data so long as you:

Have enough space to do so Don't mess with the default settings

In my case, I had the axis tick count set pretty high which was causing the labels to squish together. If you leave the tick counts at their default, or let Qt decide, it should work just fine.

@SGaist thanks I‘ll bookmark that as well

I was just googleing qtcharts source and took the firts link 🙈

@SGaist

Hi Sam,

Thank you for your hint, but my first problem was preventing the edit trigger on single click.

For the posterity I have ended up with the following solution:

Disable the textInteraction flags by default Override the QGraphicsTextItem::sceneEvent with the following: bool ValueAxisLabel::sceneEvent(QEvent *event) { if (event->type() == QEvent::GraphicsSceneMouseDoubleClick) { setTextInteractionFlags(Qt::TextEditorInteraction); bool ret = QGraphicsTextItem::sceneEvent(event); // QGraphicsTextItem::sceneevent needs to be processed before // the focus setFocus(Qt::MouseFocusReason); return ret; } return QGraphicsTextItem::sceneEvent(event); }

The textInteractionFlags should be disabled in the overridden focusOutEvent.

I'd recommend using https://doc.qt.io/qt-5.10/qxyseries.html#replace-5

Replacing points one by one destroys a cpu. The metrics for me was just not even worth measuring - it was just an immediate hell no - forget that - I need faster updates. I like declarative QML for gui as a preference but calling replace on a single point fires way too many signals and takes way too long.

I throw my QML LineSeries to a QXYSeries and call replace in c++

In the future I'll probably just declare my series in C++. I wish I could have a better supported hybrid of c++ and QML charts but I have this working very fast using useOpenGL : true; (you can also c++ setUseOpenGL(true) )