fix(preview): repair the round-clip trigger placement — it broke XAML load
The previous commit inserted the round-media MultiDataTrigger INSIDE a <Setter> instead of into the Style.Triggers collection, so every window that loads PreviewPane threw "System.Windows.MultiDataTrigger is not of type System.Windows.SetterBase" at parse time. A Debug build would have failed to open the main window at all. Caught by `AlertBoxPreviewVisibilityTests` and `AboutHubTests` in the suite, which is the reason those UI tests exist. Both green again, as is `MediaPreviewDisplayTests`.
This commit is contained in:
@@ -208,15 +208,15 @@
|
|||||||
<Condition Binding="{Binding ClipShape}" Value="Round"/>
|
<Condition Binding="{Binding ClipShape}" Value="Round"/>
|
||||||
</MultiDataTrigger.Conditions>
|
</MultiDataTrigger.Conditions>
|
||||||
<Setter Property="Visibility" Value="Visible"/>
|
<Setter Property="Visibility" Value="Visible"/>
|
||||||
<!-- A round-clipped video layer uses the same unit-circle path, or it would render in the
|
</MultiDataTrigger>
|
||||||
output and be invisible in the preview (2026-11-05). -->
|
<!-- A round-clipped video layer uses the same unit-circle path, or it would
|
||||||
<MultiDataTrigger>
|
render in the output and be invisible in the preview (2026-11-05). -->
|
||||||
<MultiDataTrigger.Conditions>
|
<MultiDataTrigger>
|
||||||
<Condition Binding="{Binding IsMediaSource}" Value="True"/>
|
<MultiDataTrigger.Conditions>
|
||||||
<Condition Binding="{Binding IsRoundShape}" Value="True"/>
|
<Condition Binding="{Binding IsMediaSource}" Value="True"/>
|
||||||
</MultiDataTrigger.Conditions>
|
<Condition Binding="{Binding IsRoundShape}" Value="True"/>
|
||||||
<Setter Property="Visibility" Value="Visible"/>
|
</MultiDataTrigger.Conditions>
|
||||||
</MultiDataTrigger>
|
<Setter Property="Visibility" Value="Visible"/>
|
||||||
</MultiDataTrigger>
|
</MultiDataTrigger>
|
||||||
</Style.Triggers>
|
</Style.Triggers>
|
||||||
</Style>
|
</Style>
|
||||||
|
|||||||
Reference in New Issue
Block a user