Re: Screen resolution problem

Hi Steve.

Would I want to put the code in the resize event?

What if I check the screen resolution upon app startup and run my
code to init the form then. I wasn't planning on letting them
resize the form by dragging it - only min and maximize.

Are you suggesting that I use a calculated position for each
control depending on the screen resolution and the size of the form?

I'm still a little confused on that point.

Thanks.
D

"Steve Barnett" <noname@xxxxxxxxxxxx> wrote in message
news:OG5kjsTiGHA.4504@xxxxxxxxxxxxxxxxxxxxxxx
Guess everyone else has made the point. Given your description of the
form, I think it would be madness to create a second form... use the
resize event to resize the content of the single form.

I think of it this way... if I have to create a second instance to support
800x600 then I'll need a third instance to support 1280x1024 and a fourth
for 1600x1024 and so on. I then find a bug or the user asks for a small
change and I find myself with a nightmare of a maintenance job. Using the
resize event means that I only retain a single copy of the code to
maintain.

Some points to be aware of... the resize event will fire when the form is
minimised, so be careful to check for this and to not resize the contents
when the form is minimised. I also code for a "minimum resolution". Once
the user can resize the screen, they'll shrink it to see how small it will
go.. What I do is decide on an arbitrary size that is as small as I want
to go and then stop resizing the controls if the user shrinks it any
smaller. It's not entirely user friendly, but I like to tell myself that
I'm protecting them from themselves.

Steve



"dman" <unlisted@xxxxxxx> wrote in message
news:OFAkNoNiGHA.412@xxxxxxxxxxxxxxxxxxxxxxx
I think my 2 options are....

1. Create a 2nd smaller form and load it if screen is 800*600

2. On the fly, resize form and move controls. There is only 1
control(grid) that I would need to resize, everything else can just
be moved.


"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:qt2dnehsresYGBnZnZ2dnUVZ_rmdnZ2d@xxxxxxxxxxxxxxx

<snipped>

Depending on the size and architecture of your app , you might also
consider
merely creating separate forms for each resolution (one for 1024x768,
and
one for 800x600). It will 'bloat' your code but makes it so much easier
in
the long run. If exec size is a problem consider supplying two products.

Like Karl pointed out, it can be a real PTIA to adjust for all cases.
(Throw
large and small fonts, and a few custom controls, into the mix and it
gets
ugly in a hurry.) It is far easier to just change your development box's
resolution - open the forms and re-design them.

Just a suggestion.

-ralph








.

Relevant Pages

  • Re: Screen resolution problem
    ... Fixing the minimum form size in the resize event will flicker and look ... 'Form Resize Constants ... Public Const gcFORM_MIN_HEIGHT = 8550 ... for an 800x600 resolution and the add code to the resize event to ...
    (microsoft.public.vb.general.discussion)
  • Re: Flicker !!
    ... Or 768x576 PAL with square pixels... ... yes resizing is bad for retaining your image resolution. ... It was used to stop the screen looking flickery. ... Now resize again to 720x576 and save for use in your project. ...
    (rec.video.desktop)
  • Re: Forms enlarging with resolutions.
    ... You can add code to your forms that will resize all ... "Ilidio Pedrosa" wrote in message ... > to 1024 the forms and controls enlarge to that resolution. ...
    (microsoft.public.access.forms)
  • Re: Screen resolution problem
    ... And what happens if they resize the desktop size while your app ... code in the resize event and give the users the "full Windows experience". ... all of the visible controls if the resolution changes. ...
    (microsoft.public.vb.general.discussion)
  • Re: Screen resolution problem
    ... the only control I have to resize. ... your app is running - do they have to close and reopen your app to get ... If you're only dealing with a small number of controls, ... resize all of the visible controls if the resolution changes. ...
    (microsoft.public.vb.general.discussion)