Any idea why this exception should occur on a gridLines.PerformAction(UltraGridAction.EnterEditMode) call?
Type: System.InvalidOperationExceptionMessage: Can't access SelectionStart unless the Editor is in edit mode.Source: Infragistics2.Win.v8.2Target Method: [Infragistics2.Win.v8.2]Infragistics.Win.EmbeddableEditorBase::get_SelectionStart()Call Stack: at Infragistics.Win.EmbeddableEditorBase.get_SelectionStart() at Infragistics.Win.EmbeddableEditorBase.set_SelectionStart(Int32 value) at Infragistics.Win.UltraWinGrid.UltraGridCell.SelectAll() at Infragistics.Win.UltraWinGrid.UltraGridCell.OnAfterCellEnterEditMode() at Infragistics.Win.UltraWinGrid.UltraGridLayout.OnEditorAfterEnterEditMode(Object sender, EventArgs e) at Infragistics.Win.EmbeddableEditorBase.OnAfterEnterEditMode() at Infragistics.Win.EditorWithText.OnAfterEnterEditMode() at Infragistics.Win.EmbeddableEditorBase.EnterEditMode(EmbeddableUIElementBase embeddableElement) at Infragistics.Win.UltraWinGrid.UltraGridCell.EnterEditorIntoEditMode(Boolean byMouse) at Infragistics.Win.UltraWinGrid.UltraGridCell.EnterEditMode(Boolean byMouse, Boolean showingDropDown) at Infragistics.Win.UltraWinGrid.UltraGridCell.EnterEditMode(Boolean byMouse) at Infragistics.Win.UltraWinGrid.UltraGridLayout.PerformAction(UltraGridAction actionCode, Boolean shiftKeyDown, Boolean ctlKeyDown) at Infragistics.Win.UltraWinGrid.UltraGrid.PerformAction(UltraGridAction actionCode, Boolean shift, Boolean control) at Infragistics.Win.UltraWinGrid.UltraGrid.PerformAction(UltraGridAction actionCode) at DandK.Vision.Client.PlugIn.POSTicket.TicketForm.ActivateGrid() in S:\Vision\Client\PlugIn\POSTicket\POSTicketForm.cs:line 5094
This is with a previous hotfix 8.2.20082.2038. As I have only seen this on production systems, I'll have to include the hotfix in the next release and see if it occurs again.Thanks.
Do you have the latest hotfix? This seems to be familiar to me, but I'm not really sure, so it might be worth looking into. If you have the latest version, when are you calling this? I wasn't able to reproduce the issue, so it's possible that it has been fixed.
-Matt