The original control is still available in the Xceed. Gets or sets a value indicating if the focus can navigate in the appropriate flow direction (e.g., from one cell to another when a cell is being edited) when the cursor is at the beginning or end of the auto-select text box. Note: This version of Masked Text Box replaces the toolkit's original control, providing a much more complete API. Obsolete namespace; see Masked Text Box (obsolete version). Value Range Text Box Represents a control that limits the input text to the format determined by the specified mask. Managing date information within the framework (or any framework, really . Please feel free to fork, and if you make happy improvements, hit me with a pull request. Do we really want to require some date, if we don’t know the correct birthdate? Folks who are good, tab through fields, and enter data. Not to mention the temptation to stop the tab-type-tab workflow by making you pick from a popup calendar. MS seems to have tossed this aside, and delivered the lame control we have at our disposal in the . There are probably reasons for this, but I don’t know what they are. The complete source code for this project (with a silly demo) is available on Github as a VS 2010 solution. For example, in entering form data for a person, we may or may not know their Date of Birth. While there are hacks and workarounds for this, most require some sort of painful validation checking in our code Never mind that the Date Time Picker is not the preferred data-entry choice for people who know how to tab through fields. Once upon a time, way back in MS Access, there existed a decent masking approach for entering date values into a textbox. If that isn’t bad enough, there is a definite data type mismatch between the manner in which the framework represents date information, and the way relational databases handle dates.
For the purposes of my project, I have achieved these requirements.The control has flaws to this point, in terms of general use (limiting the acceptable centuries comes immediately to mind), but it is a starting point.I set out to replicate the user-facing aspects of the venerable VBA Masking approach found in the MS Access Textbox, and join it with the type system such that a text string date representation could be validated, and then returned to the client code in a useful form, even if null was present.I began by inheriting from the crusty Masked Text Box control.
First order of business was to define the mask we would be using for date entry.
For my purposes, I needed to get this done fast, and the project I am working on will only ever require dates in the US-style format, so I opted to basically fix this as the only mask available. As you can see, for this work-specific implementation, I thwart attempts to change to a different mask, because the code to this point depends upon a final output format of Anything else will require more work.