Screen does not update
-
Hi, I'm a using Qt version 5.15, and vxWorks.
When running for a long time, the screen did not update.To summarize the current situation:
- This phenomenon occurred three times, each occurring after 5, 20, and 10 hours of operation.
- Only the screen is not updated and other operations proceed normally.
- Functions in code written in qml are not connected to a 'signal slot' but are called directly from C++ using 'QMetaObject::invokeMethod'.
- Tasks written in C++ work fine.
- When the qml function is called, a message should be logged because 'console.debug' was used.
So my prediction is that the Qml operation is not normal, so the screen is not updating.
So my question is whether my thoughts are correct and what is the order of QML operation when calling a QML function in C++.
-
Hi, I'm a using Qt version 5.15, and vxWorks.
When running for a long time, the screen did not update.To summarize the current situation:
- This phenomenon occurred three times, each occurring after 5, 20, and 10 hours of operation.
- Only the screen is not updated and other operations proceed normally.
- Functions in code written in qml are not connected to a 'signal slot' but are called directly from C++ using 'QMetaObject::invokeMethod'.
- Tasks written in C++ work fine.
- When the qml function is called, a message should be logged because 'console.debug' was used.
So my prediction is that the Qml operation is not normal, so the screen is not updating.
So my question is whether my thoughts are correct and what is the order of QML operation when calling a QML function in C++.
May be it is issue from your system ? Or Since you are calling qml methods directly from C++, something may be hung or got into deadlock ? There is no specific order of call. It is just method call. If it is multithread application & it may be work slightly differently.
Best approach is write a small QML application. Use timer to continuously update the qml with some random text. Observe for the period you said. This may give you the hint on where the issue exist.
