Bug Report T317359
Visible to All Users

TableView's ValidateRow event is raised multiple times when keyboard navigation is used and focus is in the NewItemRow

created 9 years ago

Hello,

We have the following code in our tableView_ValidateRow event handler method:

Code
private void tableView_ValidateRow(object sender, GridRowValidationEventArgs e) {      bool isValid = false; if (this.TypedViewModel.TryValidateEntity(e.Row as GeographicalArea, out isValid))      {       e.Handled = true; e.IsValid = isValid; return; } else {         e.Handled = true;     } } In the TryValidateEntity we handle any exceptions that might get thrown and show them in a dialog box. So, we do not let the exception bubble up to the tableView_ValidateRow event handler method. When no exception gets thrown in the TypedViewModel.TryValidateEntity everything works fine. But, when an exception does occure in the TypedViewModel.TryValidateEntity the tableView_ValidateRow gets called again?? Placing the if-else block in a try-catch-finally block does not solve this issue. Why does the tableView_ValidateRow get called twice when an exception occurs and how can we prevent the mutliple calling of this method from happening? PS. this same behavior with the TreeView_Selected event has been seen when using the TreeView control in <dxn:NavBarGroup.Content> </dxn:NavBarGroup.Content> Regards, Arjan
Show previous comments (2)
Kirill (DevExpress Support) 9 years ago

    Hello,
    I've reproduced this issue and forwarded it to our R&D team for further research. Follow our notifications to be informed about our progress.

    Thanks,
    Kirill

    S S
    Stefaan Van de Walle 9 years ago

      The provided HotFix DevExpressComponents-15.2.4.16022 does indeed resolve this issue.
      Thank you for providing the hotfix.

      DevExpress Support Team 9 years ago

        Hello,

        Thank you for your clarification. If you experience any further difficulties, do not hesitate to contact us again.

        Thanks,
        Elliot

        Answers approved by DevExpress Support

        created 9 years ago (modified 9 years ago)

        We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

        Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

          Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

          Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.