I have a data entry form which is launched as a new RadWindow above a summary page. As users maintain their data, events are fired back to code-behind to do calcs and refresh parts of the current page/window. For example, change a quantity ordered and the current inventory available quantity refreshes from the server. This works fine.
When done, users can also click Save, the current data gets saved on the server and the window is closed. This works fine.
There is a situation where a user will enter data, but not tab/enter away from the RadNumericTextBox. They just click Save without the textbox control losing focus. When this happens the Save triggers the event on the server and "simultaneously" the textbox fires its OnTextChanged event. This frequently results in the RadWindow remaining open, a server error firing, and possibly the session state getting lost. I can't define a consistent state because it's not consistent - it depends on which event gets processed first - and sometimes there's no error.I can provide more details but before I go to far, what's the protocol for preventing issues like this? Do I need to use JavaScript to set some flag in the client when events get fired to Cancel other events? That seems to require a lot of micro-management that I don't think we should have to do.
Thanks!