Hi Philipp -

I just tried your original sample app with the 9.1 and the checkboxes are showing correctly (i.e., every other one is checked and the reset are unchecked)

Have you downloaded the latest version of 9.1?

JoeM

I'm back on an older project, and it appears the bug is still present. I've switched to 2009.1, and my checkboxes are still displayed as unchecked. Any feedback appreciated....

Cheers,

Philipp

EDIT: PROBLEM SOLVED.

Due to the bug in 7.2 that set the checkboxes to an indeterminate state, I had used a style that explicitely set the IsChecked property to false. It appears that the style overrides the checkbox value even if it is being set explicitely.

Hi Joe

 Is it possible that this issue is represented in 2008.1? I just created a control with an unbound checkbox field. Whatever I do, the checkbox is never checked. Here's the code (tried to set it on Loaded event and here in InitializeRecord:

       tagGrid.InitializeRecord += delegate(object sender, InitializeRecordEventArgs e)
        {
          DataRecord rec = (DataRecord) e.Record;

          Console.Out.WriteLine("rec type = {0}", rec.Cells[0].Field.DataType);
          Console.Out.WriteLine("rec value = {0}", rec.Cells[0].Value);
          rec.Cells[0].Value = true;
          Console.Out.WriteLine("rec value = {0}", rec.Cells[0].Value);
          Console.Out.WriteLine("************");
        }

...and this is the output:

************
rec type = System.Boolean
rec value =
rec value = True
************

...and this is how the UI looks:

Have a look at Vince's answer to my post, who suggests you open an indicent that refers to issue BR30201:

This problem was recently reported to Infragistics Developer Support, and we've passed it to our developers for further investigation.  I believe the problem occurs with bound checkboxes as well.

If you are encountering this behavior, please submit a support request with Developer Support.  You can reference development issue "BR30201" when you place your request, as well as giving details about the scenario you're using (in Philipp's case, an unbound field whose value is being set in the InitializeRecord event handler).

Cheers,

Philipp