Thanks for the reply.
Currently (Qt5.1.1) binding a property between QML and C++ and change the value both side is safe because only the QML side is updated. At leas this is what i’m seeing in my tests with SpinBox and property binding:
webcam initialization => c++ => SpinBox => User
User action => SpinBox | STOP
About your solution. I don’t understand how your approach can avoid the loop if i connect the read-only property and the Q_INVOKABLE to the same QML control. Are you using two separate controls?
For now i’m using a SpinBox as input and a Label as output but it’s a quite bad solution. The spinbox is out of sync every time the camera rejects a value. Be able to stay up to date it’s definitely an important feature for a graphical interface. I’ts like i’m missing some important detail here, i can’t see a way to avoid the problem without adding a signal like “valueChangedByUser”.
↧