Propagate RenderPass command property changes to render thread


When a PipelineStateOverride or AddDefine command's properties were
changed at runtime (e.g. blendEnabled, viewport, define name/value),
the render-thread clone of that command was not updated because only
the initial append set CommandsDirty on the parent RenderPass.

A new onCommandChanged() slot is added to QQuick3DRenderPass. Every
signal emitted by a newly appended command is connected to this slot,
which marks CommandsDirty so the commands are re-cloned on the next
sync. When the commands list is cleared, those connections are
disconnected.

QQuick3DShaderUtilsRenderPassAddDefine gains proper Q_PROPERTY
accessors with change signals for its name and value members, making
those properties observable and integrated into the propagation
mechanism.

QQuick3DShaderUtilsPipelineStateOverride uses a constructor that
iterates its own meta-object signals and connects each one to the
base-class changed() signal, so QQuick3DRenderPass needs only a
single connection per command to be notified of any property change.

Pick-to: 6.11
Change-Id: Ic3a652c11a101ae1206d4eecaecd3b08f70ce224
Reviewed-by: Christian Strømme <christian.stromme@qt.io>
commitcb494b79267a2a48229a979a0368d610f480c47e
parentc56711cd927f407d348109e5f596f6a4d8436586
authorAndy Nichols <andy.nichols@qt.io>
committerAndy Nichols <andy.nichols@qt.io>
commit timeSat, 30 May 2026 06:57:26 +0000