In the sample the field layout isn't being applied to the first record; but it is being applied to all subsequent records.  I hope that clears it up.

Here is a screenshot of the behavior.  This happens in both design mode and in runtime. 

I am attaching a screenshot with the latest service relase for 11.1 build 11.1.20111.2053. What version and build are you using?

Thanks,

Diyan Dimitrov

If that's from 2053, then I may need to upgrade.  The current version of the tools we are using is 11.1.20111.1002.

I tried it with 1002 and runtime I still don’t see the issue, but I succeed to reproduce it in the design mode using both builds 1002 and 2053. Can you confirm that runtime the grid is displayed the same way as you see it design time?

Thanks,

Diyan Dimitrov

I've updated the sample to more closely reflect the program's usage of the grid (The only major difference is instead of Window we use XamRibbonWindow) and this updated sample reflects the problem in runtime now accurately as well.

Sorry this is proving so tricky!

The style that's not getting applied can't really get put above the DataSource in the xaml, because it's its own separate element, something like this:

<igDP:XamDataGrid ... ... ... DataSource="{Binding Path=MyPath}">
<igDP:XamDataGrid.FieldSettings>
<igDP:FieldSettings ... ... ...
CellValuePresenterStyle="{StaticResource MyStyle}"
>
</igDP:FieldSettings>
</igDP:XamDataGrid.FieldSettings>
</igDP:XamDataGrid>

I don't think there's any way to move the DataSource after the FieldSettings, is there?

But I'd be surprised if it's beginning to render the data before it's even processed the xaml, but you're right that it does appear to be some kind of a timing issue. That's where I'm hoping something within Infragistics code might have fixed this.

As one quick other point, I can see in the debugger that the CellValuePresenterStyle is set properly on the grid, but not on any lower level FieldLayouts or individual Fields. So it's not that it's not being set, or that it's being overwritten. It's something in Infragistics' processing of that. But I can see, using Snoop, that the default Infragistics stylings - the individual colors, that is - are being used for the errant record.

Why are you not able to flip the order of variables in the XAML code?   That's what worked for me in the end.

It looks like the rendering is a multi-threaded or multi-capable handling processor, because it starts rendering the datasource as soon as it gets it; having the formatting first gets the formatting rendering while the datasource hasn't been built.  That minor delay is what seemed to be the problem.

Not a whole lot of help, but at least a bit of clarification.

Hi - we've stumbled into a similar problem with different enough circumstances that we cannot apply this suggested fix directly. But the bottom line is that we're facing the same symptoms: set a CellValuePresenter style for use by the entire grid, but it only has effect on rows 2-n. The first row is initially unstyled, but as you scroll around, a different random row will become unstyled instead, and so on.

So my question is: is the fix suggested more of a workaround to hide an existing Infragistics issue? Might the issue surface in other ways? And if so, might it be something that's been fixed in a later release?

I will probably need to open a separate issue on this, but was hoping for some guidance in the context of Collin's original issue.

That certainly does help and has managed to solve my wonderfully troublesome problem!  I had been under the (apparently mistaken) impression that properties and in particular attached properties weren't necessarily processed in the order laid out in the xaml, but it seems I was wrong.

Again, thank you!

Hi,

The simplest way to get the desired result is to set the DataSource after setting the attached property for the layouts.

<igDP:XamDataGrid x:Name="DataGrid" 
         GridTesting:AddFieldLayoutBehavior.FieldLayouts="{Binding Path=FieldLayouts}"
         DataSource="{Binding Path=DataCollection}"  Margin="0,0,0,-134">

Hope this helps!

Thanks,

Diyan Dimitrov