Edit filtered column Then filterbar crashed

Hi, I used a GridDataBoundGrid, linked it to a data table as datasource. Defined a new filter bar and wired it to thr grid. I filtered the grid on one of the columns, say Column-A. When I make a change on any of the rows on the filtered column, application crushes.. Is this a Syncfusion bug, is there any solution?

This is corrected in our 2.0 code base.

My grid version is 2.0.2.1 ?? >This is corrected in our 2.0 code base.

Try setting the Binder.OptimizeListChangedEvent property to true. public Form1() { InitializeComponent(); this.gridDataBoundGrid1.Binder.OptimizeListChangedEvent = true; // // TODO: Add any constructor code after InitializeComponent call // }

I added the one line code under this.InitializeComponent() in the Constructor; I received "Object reference not set to an object" error. Then I moved the code at the end of my LoadData() Method in which I fill the Dataset and set the grid datasource, I received no errors but now when I choose an item in the filterbar, no filter is applied, all the rows remain the same? >Try setting the Binder.OptimizeListChangedEvent property to true. > >public Form1() >{ > InitializeComponent(); > this.gridDataBoundGrid1.Binder.OptimizeListChangedEvent = true; > // > // TODO: Add any constructor code after InitializeComponent call > // >} >

The appearance of the grid not changing is a refresh problem in the beta code (I think). After doing the filter, drag the grid on/off the screen or move another window over it so the grid is forced to repaint. I think you will see the filter was actually done, but the screen was not repainted. (This has been fixed in later code.) After you force the grid to repaint so you see the filtered results, I think if you will edit one of the entries so it no longer satisfies the filter, you will see it gracefully being removed from the grid instead of throwing an exception as before. At least this is what I see in the FilterBar sample using 2.0.2.1 and adding OptimizeListChangedEvent as above.

That was true; I added an event handler for filterBar.FilterBarTextChanged event and call the Invalidate method of the Grid; now everything is fine; Thanks! >The appearance of the grid not changing is a refresh problem in the beta code (I think). After doing the filter, drag the grid on/off the screen or move another window over it so the grid is forced to repaint. I think you will see the filter was actually done, but the screen was not repainted. (This has been fixed in later code.) > >After you force the grid to repaint so you see the filtered results, I think if you will edit one of the entries so it no longer satisfies the filter, you will see it gracefully being removed from the grid instead of throwing an exception as before. At least this is what I see in the FilterBar sample using 2.0.2.1 and adding OptimizeListChangedEvent as above.