Here's an example to illustrate the issue I found. Using a MaskedTextBox with the following mask:
so the input can't start with a number or whitespace and the rest of the value can't contain whitespace up to a total of 30 characters. This is great if you are typing from the beginning or appending to the end.
However, if the user attempts to input a space into the middle of the value somewhere, e.g., attempt to change "myValue" to "my Value", debugging the code shows me that the call to match matches the text up to the invalid character and gets rid of everything after, leaving me with "my". That's all fine and dandy and the matcher is just doing what it's told.
Now to fix this to behave how any input should behave, just block that input and leave the original value intact, I would need to use the begin and end anchors so my mask would become:
The problem is, the implementation doesn't support these Regex elements.
So, the code should be updated to have a property to set it to match the whole string to give the proper behavior or the begin and end anchors need to be supported which would accomplish the same thing. (There may also be some regex kung fu that could be applied, but I'm not a regex expert). Is this something that could be tackled in an upcoming release? Or has it already been fixed in 663 or 664?