@wasawi2 wooops sorry my newby fault!!

I just had to remove the auto in the cpp file.
Therefore:

linewidget.cpp

//![1] m_series = new QLineSeries; //![1]

linewidget.h

QLineSeries* m_series = nullptr;

Everything under control now.
Thanks again for your fast answer @kkoehne.

"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.

Hello,
I tried the library qwt and saw that the slowdown effect did not occur.
Update all my code to adapt it to the qwt library and once integrated, no type of slowdown occurs even after a couple of days. Also this library allowed me to insert better visual effects.

Thanks for the help.

I think I just figured it out by setting using a bool and setting it to false at the beginning. Then just before attaching the axis determine axis visibility. If the bool is false, set the axis visibility to true then set the bool to true. The next time thru, the bool will be true and set visibility to false. I ge both lines and only one set of scales.

if (axisXHasBeenAdded == false)
{
axisX->setVisible(true);
axisXHasBeenAdded = true;
}
else
{
axisX->setVisible(false);
}

@DrakeM said in Gaps in QLineSeries:

When using line series, we've had severe performance problems. We end up with thousands of series to handle all of the gaps and have to create parallel scatter series because we want icons for each point that aren't part of the standard icon set.

We pay a huge cost both constructing and destructing the series. Seems like it may be refreshing on each add series, but even removeAllSeries is slow. Have tried many things to suspend the painting, but with no timing effect.

Any ideas on how to have many gaps without destroying performance?

You can generate gaps by adding qQNaN()'s to the series. However, it doesn't seem to work with append() (it ignores NaN's), but setting the whole point data at once takes NaN's into account.

great! That works. With that I can spare the toggle functions at all.
Thanks!