I have added a new property to the KryptonDropButton called Splitter, a boolean indicating if the drop down button should be placed in a separate split area. This is how it looks with the drop down button in each of the four possible positions…
And just to prove that it really operates as a split button here are the tracking and pressed states for the two different areas…
If you press the main part of the button you get the Click event fired. If you press in the split area instead then you get the DropDown event. You only get one or the other event and not both.
Ideally we would not have three separate buttons called KryptonButton, KryptonCheckButton and KryptonDropButton. It would have been better to have a single button that had a type property to switch functionality. However, I do not want to change the existing controls because it would disrupt existing applications built on the Toolkit. Besides it is hardly the end of the world for the developer to choose between three button controls.
January 15th, 2008 at 9:45 pm
Great work, Phil !!
Hope we can expect another CTP Release soon …
January 16th, 2008 at 3:48 am
I actually prefer 3 different types. I don’t like over-generic controls that try to do too much at once. Then you have to fiddle with properties until you get what you want. For our control library, I’ve subclassed System.Windows.Forms.TextBox and created very specific TextBox-classes that handle just 1 type of input: WTextBox (single-line text), WTextArea (multi-line text), WPasswordTextBox (passwords), WNumericTextBox (numeric values), WDateTimeTextBox (DateTime values). Just drop one of them on your form and you don’t have to set properties like UsePasswordChar or Multiline. And each control has some unique properties that are only appropriate for that type of input (DateTimeFormat, NumberFormat, Decimals, …). Another advantage is that the source code for the individual controls is cleaner.
January 16th, 2008 at 7:59 pm
Superb