Description with steps to reproduce
Add a qDebug() inside the setInData implementation of a NodeDelegateModel.
Trigger a data update from an upstream node.
Observe the console outputting the log twice with a small time gap (~40ms).
Supporting files, videos and screenshots
Hi author,
I noticed an interesting behavior where every node's setInData function is being called twice during execution. This leads to redundant computations for each update cycle. Is this a deliberate design choice for UI/Data synchronization, or should I be handling idempotency manually within the nodes?
Qt Version
QT 5
Operating system
Windows10
Additional context
No response
Checklist
Description with steps to reproduce
Add a qDebug() inside the setInData implementation of a NodeDelegateModel.
Trigger a data update from an upstream node.
Observe the console outputting the log twice with a small time gap (~40ms).
Supporting files, videos and screenshots
Hi author,
I noticed an interesting behavior where every node's setInData function is being called twice during execution. This leads to redundant computations for each update cycle. Is this a deliberate design choice for UI/Data synchronization, or should I be handling idempotency manually within the nodes?
Qt Version
QT 5
Operating system
Windows10
Additional context
No response
Checklist