C
Charles A. Lackman
Hello,
I have been working with Visual Studio.net for a few years now and just
recently come to a problem. Up until now I have created all my programs to
be resolution specific. Most of them are written to run at 800 X 600,
others were predeterminted as to what resolution they would be written at,
based on what the individual wanted.
Now I have a client that want the program written at 800 X 600 but if the
users screen resolution is larger and they maximize the Form, he wants it to
auto size all the controls on the form to fit the new resolution, also that
the form be sizable and also perform autosize. A lot of these forms will
have custom user controls on them and multiple buttons and textboxes, etc.
I know I can place code in the Resize Event (which are based on integers
instead of doubles, to accomplish this (coding each control based on the
size of the form, but this can cause some undesized effects in fonts and
alignment (so I have learned)). Is this matter addressed in Visual Studio
2005, and is there a better way of accomplishing this?
Thanks,
Chuck
I have been working with Visual Studio.net for a few years now and just
recently come to a problem. Up until now I have created all my programs to
be resolution specific. Most of them are written to run at 800 X 600,
others were predeterminted as to what resolution they would be written at,
based on what the individual wanted.
Now I have a client that want the program written at 800 X 600 but if the
users screen resolution is larger and they maximize the Form, he wants it to
auto size all the controls on the form to fit the new resolution, also that
the form be sizable and also perform autosize. A lot of these forms will
have custom user controls on them and multiple buttons and textboxes, etc.
I know I can place code in the Resize Event (which are based on integers
instead of doubles, to accomplish this (coding each control based on the
size of the form, but this can cause some undesized effects in fonts and
alignment (so I have learned)). Is this matter addressed in Visual Studio
2005, and is there a better way of accomplishing this?
Thanks,
Chuck