Y'all,

I am getting an "An attempt was made to end the edit process while it is already in the process of being ended" error very repeatably the second time I save inserted data when starting from an initially empty grid.  I've boiled the problem code down to a very stripped down example (about 20 lines of code) which I am including in the attached file.  The steps necessary to see the error are:

1) Run the program

2) Enter some text in the insert row in the grid

3) Click "Save"

4) Enter some new text in the insert row in the grid

5) Click "Save"

 Step five will produce the error. 

I don't think that calling "EndEdit" is explicitly required to get this error, although that is the line of code where the error will be seen in the attached example.  I was also able to get a similar behavior in a version of the code without the "EndEdit" call but the steps for reproducing it that way are more complicated.

I upgraded to build 3.5.9502.16400, to no avail.

Has anyone else run into this problem?  Am I doing something invalid or is this a bug?

 Thanks,

-JLS

For anyone following this thread...

Tech support acknowledged that the behavior I noted is a bug and indicated that it would be fixed in a future version.  They also supplied the following workaround (which worked fine in my code):

 For the time being, please use the following workaround to make your code work:

   Private Sub cmdSave_Click(ByVal sender As Object, ByVal e As System.Windows.RoutedEventArgs) Handles cmdSave.Click

        grdPerformanceObjectives.EndEdit()

        _PerformanceObjectives.AcceptChanges()

         If grdPerformanceObjectives.CurrentItem Is Nothing Then

            grdPerformanceObjectives.Items.MoveCurrentToFirst()

        End If

    End Sub

 -JLS

I just encountered this bug myself.  Two grids in my application are acting weird after I insert something. When I press enter new data into the InsertionRow and press "Enter", a new row shows up in the grid area, but the same data still shows in the InsertionRow.  The odd thing about this is that it seems to only happen for the first row entered, the grid must be bound to an empty BindingList<T>, or this problem will not manifest itself.

I just happened to hover over the InsertionRow area after this occured, and a small pop-up occured saying "An attempt was made to end the edit process while it is already in the process of being ended."  I never got an exception thrown or anything else to indicate some abnormal behavior.  I just happened to move my mouse over the InsertionRow to get this to happen.

Ryan

This work-around won't work for me as the EndEdit method is the one throwing the exception on cell edit.

Do I need to contact tech support to provide a specific example?

Is there a way to check if the grid is in the process of ending the edit?

You will get an exception if there are some ValidationErrors or any other problems commiting the new data in the DataSource. 

If it's not the case, send a repro app to support@xceed.com mentioning this forum post and we'll have a look at it. 

---

Christian Nadeau
Software Developer
Xceed Software Inc.

I too ran into this bug.  This being the second round of bugs on InsertionRow, and not really liking how the whole Commiting/Canceling/CreatingNewItem cycle fit in (or didn't) with my MVVM code anyway, I re-evaluated and just plain took out the InsertionRow, instead adding a button for "add item" that adds a new blank row to the collection, which then has to be completed or removed before the overall record is saved.  Might not work in every case, but does in mine and overall involves less code in fewer places.

 -Scott

i am coming across the exact same bug too. Is there any resolution? I tried the EndEdit workaround but calling grid.EndEdit throws the same exception

Just to clarify, calling EndEdit is NOT the workaround.  That is the line of code where I encountered the bug.  The workaround was to ensure that there is a current item after the EndEdit has been called as in the following code:

         If grdPerformanceObjectives.CurrentItem Is Nothing Then

            grdPerformanceObjectives.Items.MoveCurrentToFirst()

        End If

If you're not calling EndEdit, you may need to search for an appropriate event to add this code to, I'm not sure.

 -JLS