Issues found testing with 8.0.20241.664

Posted by: abraham on 16 August 2024, 2:21 am EST

  • Posted 16 August 2024, 2:21 am EST - Updated 16 August 2024, 10:24 pm EST

    Doing new evaluations of the C1 Input v 8 controls to assess the viability of upgrades of legacy .NET 4.8 projects, we discovered the current v 8 (8.0.20241.664) C1 input controls have two annoying issues that should be fixed somehow.

    Issue 1)

    Adding the C1.Win.DbNavigator to a project that already has C1.Win.Input, C1.Win.Calendar, C1.Win.TrueDBGrid, C1.Win.FlexGrid added, causes the designer to choke: the C1TextBox control is not visible anymore in the Toolbox panel and any existing on-form C1TextBox controls cannot be edited with the Form designer anymore. See two example solutions below that demonstrate this problem.

    Issue 2)

    Setting the DataSource + DataMember for e.g. C1TextBox / C1DateEdit / C1Label to an on-form BindingSource and a named member/field/column, but with the BindingSource itself still unconnected to an underlying DataTable/DataView/BindingList, the appropriate init code for InitializeComponent() is generated. However when the application is run, the C1 Input controls throw exceptions because the BindingSource is still unconnected/empty at the time InitializeComponent() is run - that happens only after that call in the remainder of de Form Constructor code.

    C1 controls like C1FlexGrid or C1TrueDBGrid don’t have this problem, so this would be easy to fix: do not throw exceptions when the DataSource for the controls is still empty.

    It should be noted standard .NET controls like TextBox also do have the this capability of a DataBinding to a named field/member/column for a BindingSource that doesn’t have a DataSource set yet at design-time. So fixing this issue for the C1 Input controls would bring it in line with the standard .NET controls.

  • Posted 16 August 2024, 2:25 am EST - Updated 16 August 2024, 2:27 am EST

  • Posted 19 August 2024, 2:18 am EST

    Hello,

    Thank you for providing the samples. We were able to replicate the following two of the behaviors:

    1. Input controls are not visible in Toolbox after installing DBNavigator. [Internal Tracking ID: C1WIN-32788]
    2. C1TextBox and C1Label are not editable / VS deadlocks. [Internal Tracking ID: C1WIN-32789]

      We have escalated these behaviors to the development team to get further insights. Rest assured we’ll update you once we get any information.

    We are sorry, but we could not replicate issue 2, where setting the DataSource + DataMember for C1Input controls results in an exception in the designer using your instructions in the sample attached (uncomment these next two lines + set these properties using the Winforms Designer to reproduce the exception).

    To replicate the behavior, we tried to create a sample project and set DataSource + DataMember with empty binding source and got the following error:

    System.ArgumentException: 'Cannot bind to the property or column city on the DataSource. (Parameter 'dataMember')'

    We have escalated this behavior to the development team for further investigation. [Internal Tracking ID: C1WIN-32790]

    Please let us know if you are also getting the same error.

    Regards,

    Uttkarsh.

  • Posted 19 August 2024, 2:45 am EST

    @uttkarsh.matiyal:

    Issue 2) is a run-time error as indicated in the text; the exception you mention is the correct one for that. It shouldn’t occur for controls bound to a BindingSource that still has an unbound DataSource itself at the time InitializeComponent() is run.

    Looking forward to updates from the dev team.

  • Posted 20 August 2024, 12:03 am EST

    Hello,

    As per the development team,

    • C1WIN-32788 and C1WIN-32789 : These issues have been fixed and will be available in the upcoming release. (2024 v1 hotfix 2)
    • Thank you for the confirmation on “issue 2”; we’ll let you know once we have updates from the development team on this behavior.

    Regards,

    Uttkarsh.

  • Posted 20 August 2024, 12:17 am EST

    @uttkarsh.matiyal:

    That’s good news.

    For issue 2) it’s important the behaviour of the C1 Input controls is brought in line with the standard .NET controls (e.g. TextBox) and the C1FlexGrid and C1TrueDBGrid controls - these all behave correctly when bound to BindingSource members/fields/columns where the BindingSource is still unbound itself.

    Consistency across .NET and C1 controls is essential.

  • Posted 21 August 2024, 3:25 am EST

    Hello,

    As per the development team, the issue-2 you reported is a bug and ETA for the fix is 2025v1.

    [Internal Bug ID: C1WIN-32799]

    Rest assured, we’ll update you once the issue has been fixed.

    Regards,

    Uttkarsh.

  • Posted 22 August 2024, 8:07 pm EST

    Wonderful, looking forward to the fixes.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels