We've just upgraded to Infragistics WPF v10.2 from v9.2 and are experiencing some issues.
It seems as if the "BackgroundHover" property of DataRecordCellArea is ignored if the grid RowSelector Location is set to none.
This is a new issue in the latest version (with the latest service release), it worked fine in v9.2
I've created a new application and tested only that behavior to make sure that we don't override it somehow in our code and it reproduced immediately.
Code Sample:
<igDP:XamDataGrid.FieldLayoutSettings> <igDP:FieldLayoutSettings RecordSelectorLocation="None" /></igDP:XamDataGrid.FieldLayoutSettings>
<Style TargetType="{x:Type igDP:DataRecordCellArea}" BasedOn="{x:Static igThemes:DataPresenterOffice2k7Silver.DataRecordCellArea}"> <Setter Property="BackgroundHover"> <Setter.Value> <LinearGradientBrush EndPoint="0,1" StartPoint="0,0" > <GradientStop Color="#FFFADD" Offset="0"/> <GradientStop Color="#FFEDA3" Offset="0.5"/> <GradientStop Color="#FFFADD" Offset="1"/> </LinearGradientBrush> </Setter.Value> </Setter> </Style>
The only way I found to workaround this issue is by setting the "RecordSelectorExtent" to 1 instead, but it's just a hack.
Hello,
The development issue with ID of 69043 has been fixed and it is available in the latest Service Release (build 10.3.20103.2196). You can download the Service Release by logging in our web site and then going to My Keys and Downloads page.
Thank you for using Infragistics Components.
Sincerely,
Krasimir
Developer Support Engineer
Infragistics
www.infragistics.com/support
Hello Hadas,
I have logged this behavior with our developers in our tracking system, with an issue ID of 69043. I have also created a support ticket on your behalf with number CAS-62483-FSZBZ0 in order to link the development issue to it so that you are automatically updated when a Service Release containing your fix is available for download.
Infragistics, Inc.
Sorry for the late answer. I have reproduced your scenario and it looks like BackgroundHover is ignored. I will write to the development team about your issue and will get back to you shortly.
Any comments on that issue?