Qt 6

Sorry, I didn't even see the qt6 link. Thanks for the inclusion link I see that Qt Charts is rated "Not Ready" ATM. I hope the bug I submitted Sep/2019 gets fixed.

Hi and welcome to devnet, That would be a question to bring to the internet mailing list. You'll find there Qt3D developers/maintainers. This forum is more user oriented.

@Benoit-Thouy Please elaborate "compilation failed as the properties are not well defined" The warning is issued by the Clang Code Model and can be squelched by creating a new Diagnostic Configuration (or use your existing one) in Options...->C++->Code Model->Diagnostic Configuration and adding "-Wno-string-conversion" to it.

@Christian-Ehrlicher Okay, my mistake. So, after letting the program run for about 24 hours straight. It reached about 3.5 GB used. I opened another application with high memory use that pushed the physical RAM usage to 98%. At this point, the application DID release about 2 GB and is now sitting at around 1.3 GB used, but it also caused the system to become unresponsive for some time, which was probably from the virtual memory swapping. Despite that, it seems like unacceptable and unexpected behavior for an application that simply runs a timer repeatedly to eventually take that much RAM.

@iddqd-0 I don't think you can do this for MySQL, other than rolling your own code.

Thread affinity is a hard concept. QThread should be seen as a "thread handler". It has affinity with the thread that created it. The actual new thread handles the run method. Whatever you create in that method will have an affinity with the thread handled by QThread.

@Eirik said in QProperty; binding and onValueChanged: order of calls seems not to matter It may be a bug, I suggest you post on the interest mailing list where this can get more exposure (you can reference this forum thread in your mail).

You have to wait() until the thread had time to shut down. Also you should not connect Sender::finished to deleteLater but the QThread's finished signal to deletedLater.

Thank you! The website clears things up for me :)

@Christina123 Well it was good you found it. No worries. Calling the base version is ultra important in most cases when using Qt so if you walk away with that knowledge extra, it was all worth it :)

@Christina123 Use QDataStream: // QPainterPath to QByteArray QByteArray ba; QDataStream ds(&ba, QIODevice::WriteOnly); ds.setVersion(QDataStream::Qt_5_15); ds << path; qDebug() << ba; // QByteArray to QPainterPath QPainterPath path; QDataStream ds(ba); ds.setVersion(QDataStream::Qt_5_15); ds >> path; qDebug() << path; And knowing that QDataStream supports QVector then in your case the code doesn't change much: // QVector<QPainterPath> to QByteArray QByteArray ba; QDataStream ds(&ba, QIODevice::WriteOnly); ds.setVersion(QDataStream::Qt_5_15); ds << paths; qDebug() << ba; // QByteArray to QVector<QPainterPath> QVector<QPainterPath> paths; QDataStream ds(ba); ds.setVersion(QDataStream::Qt_5_15); ds >> paths; qDebug() << paths;

There are a lot of reasons for paintings to happen. Moving the window, having something else coming through said window, etc.

It should be paintEvent, not paintevent. When overriding virtual members use the override keyword in the header. It will help you catch typos like this. Also, since you're passing the path through a pointer, make sure that path object is still alive when paintEvent is called, otherwise that's undefined behavior.

@Chris-Kawa Thank you for point them out to me.

To ensure which are called use Q_FUNC_INFO in your debug lines. There's no need for the installEventFilter call. You cannot paint on a widget from a different one. The correct way is like you started with QFrame, then override paint event, call the base class implementation and do your own painting afterward.

@Ketan__Patel__0011 please do not use QRegExp, it was deprecated in Qt 5 and removed in Qt 6. Use QRegularExpression.

@Christina123 Use mousePressEvent, it provides the cursor position as parameter https://doc.qt.io/qt-5/qwidget.html#mousePressEvent