Hi Infragistics,
We have a Style for a XamNumericInput which is working well. When we attempt to apply our standard ErrorTemplate onto this Style, it doesn't seem to work.
The full style is as follows...
<Style x:Key="XamNumericInputPartNumber" TargetType="{x:Type ig:XamNumericInput}"> <Setter Property="Width" Value="50"/> <Setter Property="Margin" Value="5"/> <Setter Property="ValueTypeName" Value="Int32"/> <Setter Property="SpinButtonDisplayMode" Value="Always"/> <Setter Property="PromptChar" Value=""/> <Setter Property="Mask" Value="{}{number:1-999}"/> <Setter Property="Validation.ErrorTemplate"> <Setter.Value> <ControlTemplate> <DockPanel LastChildFill="True"> <Border Background="Blue" DockPanel.Dock="Right" Margin="5,0,0,0" Width="20" Height="20" CornerRadius="10" ToolTip="{Binding ElementName=customAdorner, Path=AdornedElement.(Validation.Errors)[0].ErrorContent}"> <TextBlock Text="!" VerticalAlignment="Center" HorizontalAlignment="Center" FontWeight="Bold" Foreground="White"/> </Border> <AdornedElementPlaceholder Name="customAdorner" VerticalAlignment="Center"> <Border BorderBrush="Blue" BorderThickness="1"/> </AdornedElementPlaceholder> </DockPanel> </ControlTemplate> </Setter.Value> </Setter> </Style>
I've attached an example of what the ErrorTemplate should look like.
Any help would be much appreciated.
Regards, ifdef
Duplicate post removed.
We've downloaded the new 14.2 Service Release and whilst it appears to have fixed this issue, it's created others.
We're now correctly seeing our custom Error Template around the XamNumericInput (in blue)...
But we're still seeing the Ingragistics built-in version (in Red) which then clashes..
Our template is defined like so...
<Style x:Key="ValidatedXamNumericInput" TargetType="{x:Type ig:XamNumericInput}">
<Setter Property="Validation.ErrorTemplate">
<Setter.Value>
<ControlTemplate>
...
</ControlTemplate>
</Setter.Value>
</Setter>
</Style>
And this should override the template in the Infragistics style.
Please could you advise.
Hi Stefan,
Any updates on this please?
Many thanks Stefan. Good news that it's being addressed in 14.2!
Will this also apply to other xam controls as well? e.g. xamMultiColumnComboEditor
We have the same issue with that, amongst others.
Hello,
There were some issue with this, which are now fixed internally for version 14.2 and 15.1. The fixes will be available in out next service releases.