Hello Jay,

Thank you for your reply. I've attached a sample that demonstrates multiple columns with the same selected background color. Based on your code snippet I don't know what the trigger is for. Keep in mind that both the cellvaluepresenter and datarecordcellarea have hover and active backgrounds that you can either set to the same color or transparent to hide the default "skyblue" color you see.

Please see my attached sample as I've demonstrated that you can selected and cell, across any column and it will only show one color.

Let me know if you have any questions.

Dear Michael,

Thanks for the sample. In your sample, if I uncomment the DataTrigger, the highlighting of selected cells do not work. Note that I have set Value = "name" below....please try it.

            <Style.Triggers>
                <DataTrigger Binding="{Binding Path=Field.Name, RelativeSource={RelativeSource Self}}" Value="name">
                    <Setter Property="Background" Value="LightGray"/>
                </DataTrigger>
            </Style.Triggers>

Note: In my actual application, I use a converter in the above DataTrigger and hence do need it. I guess, I need the BackgroundSelected property to override the Background property of CellValuePresenter - any workaround is fine too.

Thanks.

Hello Jay,

Thank you for your reply. The selected background should be updating as expected as long as you are setting the BackgroundSelected for CellValuePresenter. I've discussed this with my team and have decided to investigate this further. I will be following up shortly after I report an official development issue. As a work around, you can add a second trigger based on the IsSelected property and change the Background according to the BackgroundSelected property.

eg.

<Style TargetType="{x:Type igDP:CellValuePresenter}">           
            <Style.Triggers>
                <DataTrigger Binding="{Binding Path=Field.Name, RelativeSource={RelativeSource Self}}" Value="name">
                    <Setter Property="Background" Value="LightBlue"/>
                </DataTrigger>
                 <Trigger Property="IsSelected" Value="True">
                    <Setter Property="Background" Value="{Binding Path=BackgroundSelected, RelativeSource={RelativeSource Self}}"/>
                </Trigger>
              
            </Style.Triggers>
            <Setter Property="BackgroundActive" Value="LightGreen" />
            <Setter Property="BackgroundSelected" Value="LightGreen" />
        </Style>

Let me know if you have any questions.

Hi Michael,

Your suggestion of using a second trigger based on IsSelected works perfectly - I am all set. Thanks.

Hello Jay,

I am glad my work around has helped you. I have created case for you with ID CAS-182642-M9C8C9. You could reach your case following the link bellow:

https://ko.infragistics.com/my-account/support-activity
 
I will update you via the mentioned case, so if you have any further questions or comments please update your case.

Hello Jay,

The development issue logged was resolved and concluded to be not a bug.

The issue is happening because in our ControlTemplate we have an element that is bound to the templated parent's Background property and it also has a (templater) trigger to set the Background property of the templated parent (namely the CVP) to the SelectedBackground. Because implicit style triggers have a higher precedence than control template triggers, as seen by your demo, the Background property was not changing.

To fix this I would consider changing the control template trigger such that instead of the setter setting the Background DP to the state based DP (like SelectedBackground), it would have to be changed to target the element in the template and instead change what property it was bound to.

Here are the following workarounds.

(a) Add another trigger that sets the Background to the brush they want when its selected:

 
               <MultiDataTrigger>
                    <MultiDataTrigger.Conditions>
                        <Condition Binding="{Binding Path=Field.Name, RelativeSource={RelativeSource Self}}" Value="name" />
                        <Condition Binding="{Binding Path=IsSelected, RelativeSource={RelativeSource Self}}" Value="true" />
                    </MultiDataTrigger.Conditions>
                    <Setter Property="Background" Value="{Binding BackgroundSelected, RelativeSource={RelativeSource Self}}"/>
                </MultiDataTrigger>

 -OR- 

(b) Remove the style trigger and instead set the FieldSettings->CellValuePresenterStyle of that specific field (since style triggers have a lower precedence than the template triggers):

    <Window.Resources>
        <Style x:Key="nameCvpStyle" TargetType="{x:Type igDP:CellValuePresenter}">
            <Setter Property="Background" Value="LightBlue"/>
            <Setter Property="BackgroundActive" Value="LightGreen" />
            <Setter Property="BackgroundSelected" Value="LightGreen" />
            <Setter Property="BorderThickness" Value="0,0,1,1" />
            <Setter Property="BorderBrush" Value="LightGray" />
        </Style>
    </Window.Resources>
    <Grid>
        <igDP:XamDataGrid BindToSampleData="True" Margin="50" Name="xamDataPresenter1" >
            <igDP:XamDataGrid.FieldSettings>
                <igDP:FieldSettings
                  CellClickAction="SelectCell"/>
            </igDP:XamDataGrid.FieldSettings>
            <igDP:XamDataGrid.FieldLayoutSettings>
                <igDP:FieldLayoutSettings AutoGenerateFields="True" SelectionTypeCell="Range"></igDP:FieldLayoutSettings>
            </igDP:XamDataGrid.FieldLayoutSettings>
            <igDP:XamDataGrid.FieldLayouts>
                <igDP:FieldLayout>
                    <igDP:Field Name="name">
                        <igDP:Field.Settings>
                            <igDP:FieldSettings CellValuePresenterStyle="{StaticResource nameCvpStyle}" />
                        </igDP:Field.Settings>
                    </igDP:Field>
                </igDP:FieldLayout>
            </igDP:XamDataGrid.FieldLayouts>
        </igDP:XamDataGrid>
    </Grid>
[/code]

Of those I would recommend (b) because you will not have to worry about which property the Background should be using at the time.

Let me know if you have any questions.