Is there a compelling reason to obsolete the IsChecked property of Check Boxes and Radio Buttons?
For what it's worth, the .Net checkbox has both a Checked (boolean) and CheckState property, I thought this was an established standard. Why mess with it?
Personally, I have rarely (I think never) had a reason to use a three-state control. It's neat and different, and a way to clearly indicate an unset value, but I haven't had a reason to utilize an indeterminate state.
However, I've implemented and used thousands upon thousands of checkboxes, and a simple boolean setting has so far always made the most sense.
I would be very sad to have to change nearly 400 lines of code from a clean, easy to understand
checkbox.IsChecked = true; |
To the unwieldy
checkbox.ToggleState = |
SomeCompany.ControlNamespace.SubNamespace.SomeEnumeration.On; |
Worse still, many of these are directly connected to a simple on-off value somewhere. So I'd be going from:
checkbox.IsChecked = LightSwitch.SwitchedOn; |
To the even more gangly
if (LightSwitch.SwitchedOn) |
checkbox.ToggleState = SomeCompany.ControlNamespace.SubNamespace.SomeEnumeration.On; |
else |
checkbox.ToggleState = SomeCompany.ControlNamespace.SubNamespace.SomeEnumeration.Off; |
Am I the only one who feels the boolean property needs to be retained?
I have some performance issue in gridview and I would like to try use property EnableFastScrolling.
What happens if fast scrolling in enabled? Why it is not enabled by default?
I checked documentation: http://www.telerik.com/help/winforms/telerik.wincontrols.gridview-telerik.wincontrols.ui.radgridview-enablefastscrolling.html but there are no any details.Dim
frmDemo
As
New
FrmDemo
frmDemo .MdiParent =
Me
frmDemo .StartPosition = FormStartPosition.CenterParent
frmDemo .WindowState = FormWindowState.Maximized
frmDemo .Show()