469,898 Members | 1,586 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,898 developers. It's quick & easy.

Why would an inherited form resize itself in Visual Studio

Hi,

I have some forms in my application. Some visually inherited forms resize
themselves in Visual Studio - ruuning my previous settings. Locking the
form has no effect either.

The forms it has problems with seem to be when the inheritance structure in
greater than 2 levels deep.

It is as follows:

ViewWin - part of the MVC structure I'm using. All forms in the
application inherit from this
\/
\/
Second Level Form - these seem to be Ok
\/
\/
Third Level Form - these forms seems to resize all the time

Any ideas or known issues with this.

Regards,

Nick
Jul 21 '05 #1
11 2190
Hi Nick,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that some inherited forms will be resized
automatically at design time. If there is any misunderstanding, please feel
free to let me know.

As far as I know, if there are some controls which has anchor settings in
the parent form, the code generator will sometimes goes wrong. Here is a KB
article about this.

http://support.microsoft.com/default...B;EN-US;316560

Please check to see if this is the issue you have met. If not, could you
please let me know the version of VS.NET you're using? Thanks!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Jul 21 '05 #2
Hi Nick,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that some inherited forms will be resized
automatically at design time. If there is any misunderstanding, please feel
free to let me know.

As far as I know, if there are some controls which has anchor settings in
the parent form, the code generator will sometimes goes wrong. Here is a KB
article about this.

http://support.microsoft.com/default...B;EN-US;316560

Please check to see if this is the issue you have met. If not, could you
please let me know the version of VS.NET you're using? Thanks!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Jul 21 '05 #3
"Nick Zdunic" <ni**@ss.com.au> wrote in message
news:u_*******************@news-server.bigpond.net.au...
Any ideas or known issues with this.


This is one of the more well-known issues. The KB article mentions anchored
controls, but it seems to happen in cases where there are no controls on the
form as well, or when they aren't anchored.

The only real workaround is to not use the form designer.

Marc
Jul 21 '05 #4
"Nick Zdunic" <ni**@ss.com.au> wrote in message
news:u_*******************@news-server.bigpond.net.au...
Any ideas or known issues with this.


This is one of the more well-known issues. The KB article mentions anchored
controls, but it seems to happen in cases where there are no controls on the
form as well, or when they aren't anchored.

The only real workaround is to not use the form designer.

Marc
Jul 21 '05 #5
That's a real bummer - nice feature to have - pity it doesn't work
properly in VS.NET

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 21 '05 #6
That's a real bummer - nice feature to have - pity it doesn't work
properly in VS.NET

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 21 '05 #7
Hi Nick,

This known issue seems to be only happening in .NET framework 1.0. If
you're using .NET framework 1.1, it has to be fixed. You can also try to
download .NET framework 1.1 sp1 to see if the fix has been applied.

http://www.microsoft.com/downloads/d...54f-088e-40b2-
bbdb-a83353618b38&DisplayLang=en

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Jul 21 '05 #8
Hi Nick,

There might be some misunderstanding in my last post. This issue exists in
..NET framework 1.0. And it has been fixed in .NET framework 1.1. Could you
let me know your .NET framework version? Thanks!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Jul 21 '05 #9


1.1

I have installed the Service pack - haven't tested it yet to see if the
problem is still occuring.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 21 '05 #10
Hi Nick,

Please take your time and test it. If the problem still persists, could you
please send me a repro package, so that I can deliver my assistance more
quickly. Thanks!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Jul 21 '05 #11
Hi Nick,

Did the probelm still exist? If you need further assistance on this issue,
please feel free to let us know.

Luke

Jul 21 '05 #12

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by 23s | last post: by
2 posts views Thread by Giojo | last post: by
4 posts views Thread by Mikus Sleiners | last post: by
1 post views Thread by Waqarahmed | last post: by
reply views Thread by Salome Sato | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.