When I create 100 TextBox's, it take about 5 ms. So that is 0,05 ms. per TextBox.
When I create 100 RadTextBox's, it takes about 1335 ms. So that is 13,35 ms. per RadTextBox.
That is a factor 267 difference!
I know a RadTextBox is much more complex that a TextBox, it creates many sub controls / instances / objects / etc, but still. I must create 60 miljoen array's of 100 bytes to get the same delay / performance, so object creation cannot be it.
Now I have to requests:
- Make the RadTextBox faster (and while you are on it, maybe take a look at the other controls). Maybe with some lazy loading, reusing of objects, etc.
...or... - Make the controls resettable. For example: Give them a IResettableControl interface (with method void Reset()). Resetting the control brings it back to it initials state (all properties to their default state, all users event handlers removed from the events, etc.
When option 2 is implemented, the control can be place in a pool an be reused.
Background info: I create a lot of controls in a "factory" based on an enum ControlType (with elements like TextBox, CheckBox, etc.) This factory could facilitate pooling.
Moving the mouse over the null text, the text flickers. This behavior is observed in the following list of controls:
- RadMultiColumnComboBoxControl
- RadDropDownList
- RadDateTimePicker
It could be observed in other controls where the input element is RadTextBox and the null text property is set.
This behavior is not observed in standalone RadTextBox control.
Text is clipped in Fluent and Breeze theme
To workaround this, we can set the EnableRadAutoScale property to false.
RadControl.EnableRadAutoScale = false;
This scenario is observed in .Net6. When we place one RadTextBox control and run the application, the control is not scaled correctly.
