C1TrueDBGrid row mis-alignment regression bug (v 10.0.20261.813)

C1TrueDBGrid row mis-alignment regression bug (v 10.0.20261.813)

Posted by: abraham on 26 August 2026, 12:21 am EST

• 

  abraham

  • Post Options:
  • Link
    Copy

  Posted 26 August 2026, 12:21 am EST

  The latest version of the C1TrueDBGrid control with version 10.0.20261.813 introduces an annoying regression bug that wasn’t there in the previous version 10.0.20261.796 (or any other previous version, not even in NET Framework 4.8):

  When the underlying DataTable is refreshed/reloaded to which the C1TrueDBGrid is connected to via a BindingSource and DataView, and the previous current row index wasn’t 0 … after the data reload the current row index of the C1TrueDBGrid goes to 0 while the BindingSource.Position itself keeps the correct previous value - all all other C1 controls also display the correct row info (e.g. DbNavigator, C1FlexGrid, C1TextBox).

  This causes the C1TrueDBGrid to be mis-aligned to the actual BindingSource.Position value. A manual command by sending the C1TrueDBGrid ‘ResumeBinding()’ fixes the row mis-alignment but this is an ugly work-around and was not necessary for any previous version of C1TrueDBGrid.

  Please find attached a Visual Studio solution exhibiting the regression bug with a full explanation. When downgrading the version of C1.Win.TrueDBGrid NuGet package to the previous 10.0.20261.796 version the bug disappears.

  Currently I’ve downgraded my projects to this previous version - but a fix would be highly welcome.C1TrueDBGrid row Bug.zip

• 

  vivek.singh

  

  • Post Options:
  • Link
    Copy

  Posted 27 August 2026, 2:04 am EST

  Hello Abraham,

  Thank you for providing the reproducible sample along with the details.

  We were able to observe the mentioned behavior on our end with version 10.0.20261.813. We are getting in touch with our development team for further investigation. Rest assured, we will update you as soon as we have more information from them.

  Best regards,

  Vivek Singh