I have a customized rad window in my app that when pressed spawns another rad window. This child rad window will appear on top, as it should, and will accordingly have focus with the parent rad window and everything else on the page 'blacked out' (unable to receive foucs). This works good..
My issue is if this button that spawns the child window is double clicked, and not just double cliked, but done so very fast. I know this is a pretty rare occurence but QA has noticed. What happens is that the first click spawns the child rad window, as it should, but the second click (when done very fast) appears to give focus back to the parent child window before the spawned child window could 'black out' the parent window and page, and lock down the focus. I end up with the child window spawned and visible (but inaccessible), but the parent window still accessible and with focus...
All that the button handler code does is instantiate the rad window, call ShowDialog() and even BringToFront(). (I've tried with/without BringToFront() call). It seems as though the second button click is being processed before the child window's lock down is performed, giving focus and accessibility back to the parent window...
I have been able to replicate this behavior in a very simple, stripped down, sample project, which I have attached for reference. I have also attached a screenshot image, taken from the results of the sample project, to illlustrate the erroneous state.
Please let me know if you need anything else provided.
[ EDIT: I am unable to attach .zip files to this form posting, only images, so I attached the image. I have my company looking into renewing the support license now...Is there somewhere I can email this test project?]
Thanks for the help,