Hi,

I ran your sample and I do see that the behavior here has changed. I could not reproduce the behavior you described with the latest service release of 12.1, but I do get it with 11.1, so it looks like this change occurred in a service release for 11.2 and up.

Anyway... the solution the problem seems very simple. Remove the call to DataBind. This method is essentially useless - setting the DataSource or DataMember on the control implicitly DataBind's it, so there is never any reason to call this method.

Hm... after posting, I took out the DataBind call and it doesn't seem to make any difference.

I got it to work like this, though:

private void Form1_Load(object sender, EventArgs e)
        {
            var rnd = new Random();

            for (int i = 0; i < 10; i++)
            {
                ultraDataSource1.Rows.Add(new object[] { rnd.Next(200).ToString() });
            }

            ultraGrid1.DataBind();
            //ultraGrid1.ActiveRow = null;
            this.BeginInvoke(new MethodInvoker(this.SetActiveRowToNull));
        }

        private void SetActiveRowToNull()
        {
            ultraGrid1.Update();
            ultraGrid1.ActiveRow = null;
        }

Hi Mike,

Thanks for the response. I have version 12.1.20121.1001 of the Infragistics 12.1 DLLs on my machine so the change in behavior happened sometime after this release. 

Your sample code does work however is there a reason this functionality was changed?  There is a large amount of code that will need to be changed to add BeginInvoke methods and I'm sure I'm not the only person this change in behavior effects.  The main reason I  set ActiveRow = null is because I don't want a row highlighted by default when the user first sees the grid. If the user clicks on a row then I do want it highlighted to show it is the ActiveRow. Any suggestions?

Hi acozzi,

I created CAS-114766-W9L3R5 to track this issue and I have submitted it to our engineers for them to research.

Thanks guys. Hopefully its a quick fix that can be put into a Service Release.

An initial test of setting SyncWithCurrencyManager to false is working. We are going to test additional grids in our application and will let you know if we find any issues. Thank you very much for helping us resolve this issue.

Hi,

I just wanted to let you know that we have looked unto this issue and it turns out that we cannot fix it. The current behavior is correct, even thought it's a breaking change.

This came about as the result of a bug fix. The original bug happened at design-time. Basically, when you set the grid's DataSource, the grid would perform a bunch of metrics calculations and as an incidental part of that process, the grid also ended up synching it's ActiveRow with the current position of the DotNet CurrencyManager. This was never intentional, and performing these metrics calculations at the time of binding, before the grid painted, cause the design-time experience to be unstable. Simply dirtying anything on the form would cause the grid's column widths to change slightly ever time. So the metrics calculations are now deferred until after the grid paints. 

I know you said the BeginInvoke workaround was not ideal, so I have a couple of other suggestions.

1) Set SyncWithCurrencyManager to false. This is much simpler and easier than BeginInvoke and unless you are binding the grid and some other controls to the same data source and you need them to stay in synch, it won't make any difference in your app - in fact, it will be slightly more efficient.

2) Use the grid's Paint event:

bool flag = false;
        private void ultraGrid1_Paint(object sender, PaintEventArgs e)
        {
            if (false == this.flag)
            {
                this.flag = true;
                this.ultraGrid1.ActiveRow = null;
            }
        }