Clicking a button and pressing Enter key act different in MDI clie

[Jeffrey Tan[MSFT]]

Hi George,

Sorry for letting you wait for so long.

For these days, I have contacted the product team for #3 issue, then the
product team has confirmed this issue as a bug. Below is the workaround:

Create a new form to inherits the Form class and overrides its
UpdateDefaultButton function. The code is:
Public Class MyForm
Inherits System.Windows.Forms.Form
Protected Overrides Sub UpdateDefaultButton()
' Do nothing.
End Sub
End Class

In the MDI form, inherits the Form from our inherited form instead of the
original form class.
Public Class Form1
Inherits MyForm

Hope this helps.
===========================================
Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Jeffrey Tan[MSFT]]

Hi George,

Have you viewed my lastest reply? Does that workaround make sense to you?
Please feel free to tell me, thanks.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Guest]

Hi George,

Have you viewed my lastest reply? Does that workaround make sense to you?
Please feel free to tell me, thanks.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

 

[Guest]

Hi Jeffrey,

YES! I got to try it yesterday. Don't understand why all I have to do is put
the code in the base form. Thought I would have to put it in every form.

I've come up with a workaround for the forms not filling the client area and
sometimes not positioning correctly. I've changed the FormBorderStyle to None
(this didn't work before your last workaround) and added a timer to the
Activated Sub. It seems that anytime the Activated Sub took a long time
because of processing or and Open/Save dialog the window didn't fill
correctly. In our App we could end up requesting a file or doing thousands of
database lookups (in our test we do 100,000). Right now the timer interval is
1 second and we do our processing in the TimerEventProcessor Sub.

We also found that if you:
1. Show form2
2. Switch to form3 on a button click
3. Show form3
4. Switch back to form2 on a button click
5. Show form2
6. Switch back to form3 by program control
7. Show form3
The form that gets displayed is form2 and not form3. We fixed this by
skipping #5. Don't understand why but anything that works can't be bad.

Other comments: With the client filling properly the flicker is not as
noticeable. Also, we picked up 1/2 to 3/4 inch of vertical space that we
really needed in some forms.
Will any of these problems be fixed? Will a KB article be written so the
next victim will not have to spend 50 to 100 hours figuring this out.

I'm not sure we resolved everthing. I need to read back through all the
threads. Our App looks a lot better and we shipped two CD's today to key
customers for them to try.

Thanks
George

 

[Guest]

Jeffrey,
Continuing at "MDI Client Problems"