As already mentioned in another post in this forum, I experienced a low performance on instantiating C1DateEdit controls; e.g. 15 C1DateEdit controls on a form take 7 seconds for instantianting in the InitalizeComponent() section of the form (just the lines ' Me.C1DateEdit1 = New C1.Win.C1Input.C1DateEdit') . The same form with 15 WinForms DatePicker controls takes below 50 milliseconds...
used C1Input version is 2.0.20073.33104
I tried also pre-release 2.2008.2.33204; here instantiating of C1DateEdit control is much faster, but the part of the designer code that assigns some properties to the Calendar part of the control is very time-consuming - I measured about 0.3 seconds for setting up the properties of one single C1DateEdit control.
I think this should be investigated... Thanks for reply / support!
...after playing around for some hours with this issue, I found the following: When no properties of the Calendar-part of the control are set in the designer code, then performance is ok - but there is a little (acceptable) delay when opening the calendar drop-down for the first time. Perhaps the calendar-properties (set by designer code) should be "cached" in the control instance and applied at first opening the calendar? The little delay is more user-friendly than waiting some seconds until form is shown.
Another idea: optional ist should be possible to use the calendar of the OS; for example the Vista-Calendar is great and it would be nice to get it in the C1DateEdit.
btw: Your controls are very good work!
Regards,
Robert