I use numeric edit controls quite a bit, and I've come across the situation where the user has set a new value in the control but has not "committed" it in the sense that the enter key is not used nor have up/down arrows been used nor has the control lost focus. When another control is then cleft clicked with the mouse (e.g. a "start" button") the numeric edit control continues to display the altered value, BUT
There's no value changed, leave, or validated event generated !? I'm missing something very basic here ... seems to me that these events should all be generated when the focus changes to the start button? If I could respond to a Leave or lost focus event then I could at least maybe try to force a commit onto the numeric edit, even if the normal event model doesn't do that on leave or lost focus.
Does anyone know where I can find a good description of the windows control event model? Seems to be a very dense topic.
I can use a text changed event to capture the new value, at the expense of the callback getting invoked lots of times as the text changes as the new value is entered into the control - but that seems excessive. I set the validation to be triggered by the change event but that just results in the validation apparently discarding the intermediate change to the text.
I suppose the answer might be "don't do that" - the operator just has to know that it's not enough to simply change the text in the control - either use the enter key, or use the up/down arrows to ensure that the new value has been accepted.
