Large Child Form Question
Ron Cichoski
I'm having a problem with a large MDI child form (larger than the MDI
parent can be). First, when I load the child form it automatically makes
itself logically smaller than the parent. I can then resize by pulling the
top up, then moving the form down, then pulling the top up, then moving the
form down, and on and on until I can move the parent scroll bars and see
the whole child form. This is not acceptable. I want the child form to
remain sized as is. Furthermore, I want to automatically maximize the child
form and don't let the user at the min/max buttons. This makes it even
worse because the parent scroll bars then disappear no matter what. Anybody
have any idea why VB acts like this or have a solution? A "scrollable
panel" on the child form as I have seen with other development tools would
work. I would like the parent scroll bars to work but will settle for the
scrollable panel. Any help? Thanks!
Ron Cichoski
rcic...@adventcon.com
Greg Spence
I may be able to help with your form question, but can't do anything
about your large child. <sorry> :)
First I have to wonder what kind of application would force a person to
scroll around a screen thats too large to fit into a viewport, but with
all the possibilities out there I won't dwell on it. (Scrolling
viewports are a very bad design in my humble opinion.)
If you want the child form to be a fixed size, set the form border type
to "Fixed Single" or "Fixed Dialog". It will no longer be resized by
the MDIForm. MDIforms automatically negotiate the size and position of
all child forms that are sizeable. You can however modify the size with
code after its been loaded. If you want to maximize the child form
automatically when its loaded, set the Windowstate to Maximized in the
design environment, but you can forget about scroll-bars if you do
this. A maximized form will fit its parent exactly.
What you are asking for sounds like an odd combination and there must be
other ways to get the same functionality using a more "standardized"
approach.
Greg
John Conley
Whenever you have so many controls on a form, it just can't fit within its
parent form, that is a red flag that the development team has not spent
reasonable amounts of time planning and designing the architecture of the
system. In my years of developing and using Windows systems (including
complex client-server systems), I have have yet to find justification for
scolling forms. Break your form up into logical units that are both
practical for the system architecture and user-friendly.
John Conley
Samsona Software
http://www.samsona.com
Ron Cichoski <rcic...@adventcon.com> wrote in article
<01bc4ea5$fb92bf00$46cb...@adventco.flashnet>...