ColorGallery SelectedColorChanged issue

[User3290]

This issue is continuation of the previous topic
#398 you marked as resolved for 5.0 version of fluent

But at current moment i continue receive an old value in the handler of command, although your code is fixed

<fluent:ColorGallery x:Name="CellFillColorPicker"
                                                     Mode="ThemeColors"
                                                     IsAutomaticColorButtonVisible="False"
                                                     ThemeColorGridRows="0"
                                                     Columns="10"
                                                     IsNoColorButtonVisible="True">
                                    <i:Interaction.Triggers>
                                        <i:EventTrigger EventName="SelectedColorChanged">
                                            <i:InvokeCommandAction Command="{Binding BackgroundColorCommand}"
                                                                   CommandParameter="{Binding ElementName=CellFillColorPicker, Path=SelectedColor, Converter={StaticResource ColorToStringConverter}}" />
                                        </i:EventTrigger>
                                    </i:Interaction.Triggers>
                                </fluent:ColorGallery>

In addition converter is

public object Convert(object value, Type targetType, object parameter, CultureInfo culture)
        {
            var color = value as Color?;
            if (color == null) return "";
            var val = color.Value;
            return $"rgba({val.R},{val.G},{val.B},{val.ScA})";
        }

---

Environment

• Fluent.Ribbon v5.0.0.8
• Windows Server 2012R2
• .NET Framework 4.6.1

[batzen]

That's strange. Will have a look.

[batzen]

Ok, now i got it.
The event is fired during the property changed callback. During that time bindings to that property are not updated yet, so the command in your EventTrigger is invoked with the old value.
Will make invocation of the event async, as that's the only way to break out of the chain.