Log in to start a topic

C1DbNavigator Resizing/Lay-out Bugs (v. 8.0.20242.700 - .NET 9.0)

Posted by: abraham on 8 May 2025, 10:59 pm EST

  • abraham

    Posted 8 May 2025, 10:59 pm EST - Updated 8 May 2025, 11:09 pm EST

    C1DbNavigator Item nr-sizing Bug.2025-05-09.zip

    See attached bug demo solution for the C1DbNavigator with full instructions on how to repeat.

    Issues:

    • the editor (current record nr) section of the C1DbNavigator is too wide
    • even when AutoSize = true, the C1DbNavigator grows but never shrinks when the record count gets down to much smaller number.
    • when the DataSource is re-connected to a much large data-set; upon re-connection the C1DbNavigator is not performing an auto-size PerformLayOut() properly - resulting in displaying the total record count without sufficient space.
    • when separate BindingSource.ResetBindings(false) calls are issued to the DataSource of the C1DbNavigator - the auto-sizing/PerformLayOut() still does not occur although the C1DbNavigator does fire the RecordListChanged event and knows the correct record numbers.

    When the C1DbNavigator is bound to a BindingSource, a call to BindingSource.ResetBindings(false) should always result in an auto-resize/lay-out action. And a reduced total record count should lead to shrinkage of the control.

    Our ‘interim work-around’ is to subclass C1DbNavigator and subscribe to the RecordListChanged event to call C1DbNavigator.PerformLayOut() separately, but this is not preferred of course.

    PS: we did not experience these issues with the .NET 4 version of the C1DbNavigator control - they popped up during our migration efforts.

  • kartik.dua

    Posted 9 May 2025, 12:04 pm EST

    Hi,

    Thanks a lot for providing the detailed steps and sample project to reproduce the issue. We have reported it to the development team for further investigation. We will let you know as soon as there is an update from their end.

    [Internal Tracking ID: C1WIN-34016]

    Best Regards,

    Kartik

  • abraham

    Posted 5 August 2025, 1:25 am EST

    Any update on this issue?

  • kartik.dua

    Posted 5 August 2025, 7:58 am EST

    Hi,

    The ETA for this issue fix is the 2025v2 release. We will let you know as soon as the release is available for download.

    Best Regards,

    Kartik

  • kartik.dua

    Posted 26 March 2026, 3:31 am EST

    Hi,

    We are glad to let you know that this issue has been fixed in the latest 2025v2(761) hotfix 2 release.

    Best Regards,

    Kartik

  • abraham

    Posted 27 March 2026, 1:23 am EST

    That’s great - just tested and confirmed this is now solved; we can restart migration.

  • abraham

    Posted 7 April 2026, 5:15 am EST - Updated 7 April 2026, 8:29 am EST

    Just an update - the latest release 2025v2 Hotfix2 does fix the autosize issue for the display of the total number of rows/items (that now is shrunk when necessary), but the issue of the too wide display of the editor section where the current row/item number is displayed is still there. The editor section of the C1DbNavigator control also needs to auto-size depending on the actual row/item number.

    The same uploaded demo solution can be used to showcase the issue.

    Tested using .NET 10 and version 10.0.20252.761 of C1DbNavigator

  • kartik.dua

    Posted 8 April 2026, 5:04 am EST

    Hi,

    Thank you for sharing the details. We could see the behavior you mentioned. We have shared the observations with the development team to get their insights and will let you know the updates as soon as possible.

    [Internal Tracking ID: C1WIN-35220]

    Best Regards,

    Kartik

  • abraham

    Posted 12 August 2026, 1:51 am EST - Updated 12 August 2026, 1:53 am EST

    Just re-evaluated this issue with the new version 10.0.20261.813 but the problem persists despite the release history saying this:

    Fixed an issue where the page number text box did not resize dynamically based on the total page count while maintaining the overall navigator width.

    If my sample solution (already submitted) is compiled with this latest version, with both the larger and smaller data-set the editor section of the navigator showing the current page still is far too wide and not really sizing dynamically to what’s needed for just the current record nr.

  • kartik.dua

    Posted 12 August 2026, 7:40 am EST

    Hi,

    We checked the behavior with the latest 2026v1(813) HF2 release and confirmed that the issue is fixed in your sample project.

    Please note that as per the fix, the Current-Page textbox will automatically resize dynamically to ensure that the overall navigator width is maintained, unless required to accommodate a very large number.

    In your sample, the Current-Page textbox is expected to fill the available space within the control and should not increase/decrease the overall navigator width unless required. Previously, the same textbox increased the overall width of the control, which has now been fixed.

    The behavior you mention would require the Current-Page textbox to resize with every page change, which would result in the overall width of the control changing. This does not seem to be the expected behavior. The expected behavior is for the Current-Page textbox to, by default, fill the remaining space in the control after accommodating the navigation buttons and the Total-Page-Count label.

    Best Regards,

    Kartik

  • abraham

    Posted 13 August 2026, 12:31 am EST

    Thanks for the info - but the C1DbNavigator has an AutoSize property which would be expected to just that: to expand the size according to the display needs for the record nr and total nr of records? What would be the meaning of AutoSize currently?

    In the .NET 4.8 version of the C1DbNavigator the auto-sizing worked exactly like that. The navigator would just grow/shrink to the size it would need to display both current and total nr of records.

  • kartik.dua

    Posted 13 August 2026, 2:51 am EST

    Hi,

    We completely understand your point of view in this case. We are currently discussing the current and expected behavior with the development team to get their insights on this. We will let you know the updates as soon as possible.

    [Internal Tracking ID: C1WIN-35553]

    Best Regards,

    Kartik

Need extra support?

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

Learn More

Forum Channels