Have a XamWebGrid in a Silverlight User Control contained in a popup window. I have a method wired up to the RowExitingEditMode event of the event. If I am in the middle of editing the description, leave the cursor in the text box, and yet hit the upper right hand 'x' to close the popup window, the event for RowExitingEditMode on this grid will fire later on when I am on another page.
So, it seems like the handle for the event is not being released, which likely is postponing garbage collection, which could result in a memory leak.
I am assuming that I could do something to work around this, I am just not sure what as the close event is in the popup window, and this event which is dangling is in the user control...
Any tips would be appreciated...
I neglected to point out that the way that the event handlers are wired up are not dynamic. They are more of the type:
220
221 Private Sub dgetc_RowExitingEditMode(ByVal sender As Object, _
222 ByVal e As Infragistics.Silverlight.ExitEditingRowEventArgs) _
223 Handles dgetc.RowExitingEditMode
Hello Alan,
I think this behavior is expected since when you click on the close button of the dialog window the XamGrid remains in editmode and the RowExiting/ed EditMode events will fire only when the cell lost focus or any other element receives the focus. You can also noticed that when the you click on the close button the events will not fired unless you click somewhere on the main page.
One possible resolution is to handle the WindowStateChanging event of the dialogwindow and call ExitEditMode method. For more details you can check out the attached sample project.
Let me know if you have any questions with this matter.