B
BuddahDog
Just found something kinda fascinating.
When you have a form with minimizeBox = false (OK Button), and you
have a user who is by nature a "double clicker" - your closing events
for that form will actually fire multiple times (even if you set a
breakpoint in Debug mode, the OK button can still be clicked and will
queue up closing events!)
Any code you have in your OnClosing or Closing event handlers will be
run multiple times. Hardly an efficient use of resources, and, as I
can testify to, can cause some really unpleasant suprises.
I imagine this is because the title bar is native and not really part
of the app, but it sure seems like a bug to me. One would think that
it should stop firing events unless the closing is cancelled.
Has anyone else seen this behavior?
Anyone from MS aware of this? Is it, per chance, on the radar for SP2
(seems to be a lot of "Title Bar Blues" fixes in SP2 - just hoping
this is one of them.)
When you have a form with minimizeBox = false (OK Button), and you
have a user who is by nature a "double clicker" - your closing events
for that form will actually fire multiple times (even if you set a
breakpoint in Debug mode, the OK button can still be clicked and will
queue up closing events!)
Any code you have in your OnClosing or Closing event handlers will be
run multiple times. Hardly an efficient use of resources, and, as I
can testify to, can cause some really unpleasant suprises.
I imagine this is because the title bar is native and not really part
of the app, but it sure seems like a bug to me. One would think that
it should stop firing events unless the closing is cancelled.
Has anyone else seen this behavior?
Anyone from MS aware of this? Is it, per chance, on the radar for SP2
(seems to be a lot of "Title Bar Blues" fixes in SP2 - just hoping
this is one of them.)