All in the morning,
I design applications of several compact structures, and something that is always What we call Yorkshire Bank syndrome (ybs) is a way to stop it. After cash points in the Yorkshire Bank, YBS has been lovingly named, due to the fact that his screen is very slow, and one of my colleagues thought while pressing the button twice that he did not press the button and Instead of finishing, the drawing of 100 pounds has ended, he wanted £ 20 (the "cash without receipt" and "100 pounds" buttons were assigned to the same button on two different screens).
Actually, I load all my forms with a splash screen, the beginning of the application and every other form is a public event called Initialize (). To show a form, I used the session. Instance.formname The initial () method normally calls any form reset or data loading, so in turn the cursor is also set as that method. The problem arises when a user clicks on a button to show a form, form load, but if they click on the screen in the meantime, that screen click is passed from the form that is currently loaded Is happening (but not shown).
For example, I click on a button to show a form and then click the bottom left of the screen. In most of my CF apps, the lower right button has a back button which sets DialogResult. Cancel so once the load is over, the form is not visible as the back button is clicked, even if the form is never shown.
I have tried many things in which it is included. Enable = false start of beginning (), but it appears that the click is stored in the background and then the event clicked on the screen is removed when loaded.
So, now I'm wondering if there is a way to reject any mouse input during my loading and only enable it again before my form. ShowDialog ()? Or is anyone any better idea about how to achieve this?
Chris Tech created ApplicationEx as part. This allows you to get every Windows message that receives your app.
An example of its use.
Comments
Post a Comment