Posted 1 May 2025, 3:53 am EST
At about 40% of doing a full LOB migration project we ran into an interesting bug for both the C1TextBox and C1DateEdit (and possibly other C1 controls as well) which has caused the migration to be paused again.
Please find enclosed a VS 2022 solution that demos the bug. The Form shows instructions on how to reproduce it.
This bug seems to occur under the following conditions:
-
C1TextBox or C1DateEdit (both part of a TabPage) are bound to a BindingSource which in turn has the DataSource set to a DataView for which any RowFilter changes will determine whether the DataView has any available DataRowView objects or not.
-
as long as the BindingSource and its connected DataView has rows available - the C1 controls behave just fine.
-
when a DataView RowFilter update causes the DataView to be empty, the C1 controls automatically switch to ‘Enabled=false’ mode as soon as the TabPage that hosts them is activated.
-
but even when the DataView RowFilter is changed/de-activated and the DataView has rows available again; the C1 controls remain stuck in Enabled = false mode, and cannot be edited anymore (although data is being displayed). The C1 controls become read-only incorrectly.
-
please observe the standard .NET TextBox and CheckBox show the correct behaviour
I’ve included the same DataTable columns with identical .NET and C1 controls so the difference in behaviour can be observed clearly. The lock-up of the C1TextBox and C1DateEdit controls in Enabled = false mode is clearly a bug.
We discovered this bug as one of our complex forms that uses a similar config worked fine in .NET 4.8 yet locked-up in the migrated .NET 9 project.
At the moment we can’t continue with our migration so a fix is greatly appreciated.
