Hi-
I'm using the Radspineditor for numeric entry. It has a lot of conveniences that I'd like to keep, rather than switching to an entirely different control. One problem that we're running into though is an inconsistency in the way validation is getting handled:
When a character is appended to the text in the editor (let's say it already contains "0.00000"), most non-numeric characters will automatically be rejected- This sounds a windows "beep".
Some symbols, like an open-parenthesis or an underscore, don't cause the beep, but are still rejected. I've noticed that these symbols will also cause the "Validating" event for the RSE to fire off, while the non-numeric characters mentioned earlier will not. Even if I do nothing in my "Validating" event code, the offending character is rejected.
My task is to try to make the character-by-character validation behavior consistent, but I haven't found a way to do that with the events that are available. I need to always know during the validation event when a character will be rejected. Currently, I don't have any visibility of that: The beep-rejected characters don't fire the Validating event, and when Validating fires for the silently-rejected characters, I can't see the true text in the control.
Any suggestions? Is there something I'm missing?
thanks!
I'm using the Radspineditor for numeric entry. It has a lot of conveniences that I'd like to keep, rather than switching to an entirely different control. One problem that we're running into though is an inconsistency in the way validation is getting handled:
When a character is appended to the text in the editor (let's say it already contains "0.00000"), most non-numeric characters will automatically be rejected- This sounds a windows "beep".
Some symbols, like an open-parenthesis or an underscore, don't cause the beep, but are still rejected. I've noticed that these symbols will also cause the "Validating" event for the RSE to fire off, while the non-numeric characters mentioned earlier will not. Even if I do nothing in my "Validating" event code, the offending character is rejected.
My task is to try to make the character-by-character validation behavior consistent, but I haven't found a way to do that with the events that are available. I need to always know during the validation event when a character will be rejected. Currently, I don't have any visibility of that: The beep-rejected characters don't fire the Validating event, and when Validating fires for the silently-rejected characters, I can't see the true text in the control.
Any suggestions? Is there something I'm missing?
thanks!