[BUG] Image tint color behavior doesn't get applied from DynamicResource or ViewModel

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

On setting the IconTintColorBehavior in Image, the TintColor property is working on setting colors directly or by any StaticResource. But it isn’t working when setting the TintColor as DynamicResource or a binding property from ViewModel.

Expected Behavior

<Image HeightRequest="30" WidthRequest="30" Source="ic_notification"> <Image.Behaviors> <toolkit:IconTintColorBehavior TintColor="{Binding ChangedColor}" /> </Image.Behaviors> </Image>

This should also work like it was working in XF with the Effects.

Steps To Reproduce

1. Open and run the solution from reproduction repository
2. Click the change button & see there is no effect.

Link to public reproduction project repository

https://github.com/hemantbeast/StatusBarSample/tree/tint_color

Environment

- .NET MAUI CommunityToolkit: 3.0.0
- OS: Mac OS 13.0.1
- .NET MAUI: 7.0

Anything else?

No response

[programatix]

I tried this,

<ImageButton Source="...">
  <ImageButton.Behaviors>
    <toolkit:IconTintColorBehavior
      TintColor="{AppThemeBinding Dark=#ff0000, Light=#00FF00}"
      BindingContext="{Binding BindingContext, Source={RelativeSource AncestorType={x:Type ImageButton}}}" />
  </ImageButton.Behaviors>
</ImageButton

and it caused System.InvalidOperationException: ‘Operation is not valid due to the current state of the object.’

Perhaps the developer should provide us, the dummies with some sample in the documentation?

[brminnick]

Thanks @pictos!

Could you do us a favor and update our Community Toolkit docs to add this info? I know it’s a bit repetitive since the .NET MAUI docs already document it, but I imagine we’ll continue to get Issues + Discussions opened around this topic if we don’t.

I think the best way for us to implement this information in every Behavior doc is to add a new file, communitytoolkit-behavior.md, to the includes/ folder, similar to how we created communitytoolkit-converter.md to describe common functionality included in all converters.

Once includes/communitytoolkit-behavior.md is created with this binding information included, then we can add it to each *-behavior.md doc file, similar to how we include the snippet from communitytoolkit-converter.md in each Converter doc.

Once it’s documented, let’s close this Issue.