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.
