Well in the past I didn't worry about such things, except of course to make
sure that I never created a form that was bigger than 400 x 600 pixels, but
in this case I'm doing some strange re-sizing at runtime depending upon
whether are not some combination of groups are opened or closed, and taking
into account the individual opened height of those that are...then re-sizing
the height of the form dynamically so that the scrollbars don't appear.
This will be an option of course but as I began working out the mechanics it
started to bother me that perhaps all these little adjustments may cause me
problems at different resolutions than what I design it at.  Perhaps not but
as I've never done any re-sizing on my own like this at runtime I thought it
might be a good idea to start thinking about it! <g> I am in the process
right now of setting up a dummy model to see what happens so that I'll know
for sure.  

>From "Robert Meek" 
Personal e-mail:  [EMAIL PROTECTED]
dba / "Tangentals Design"
Visit us at:  www.TangentalsDesign.com
Home of "The Keep"!

Member of:  "Association of Shareware Professionals"
Moderator for:  "The Delphi", "Delphi-DB", and "Delphi-Talk"
programming lists at elists.org, and "DelphiTalk.net"
at www.DelphiTalk.net


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Jim Burns
Sent: Wednesday, March 16, 2005 10:14 PM
To: 'Borland's Delphi Discussion List'
Subject: RE: Resizing w/Constants vs. Variables as a baseline minimum D2005


>       In order to make this solution viable for all 
> resolutions I thought

In order to make any program work for all resolutions, then don't do
anything regarding resolutions.  100x100 is 100x100 in ANY resolution.


> say I want to enable the app for 
> the four most
> commonly used resolutions, 800 x 600, 1024 x 768, 1152 x 864, 
> and 1280 x 768.

A programmer doesn't have to do anything to "enable" an application for any
resolution.  Unless you desire to "scale" the application so it "looks" the
same at any resolution, which is a silly thing to do, is offensive to the
user and contradicts 99.9% of /your/ software experience, don't fiddle with
anything!  :)


The common issue with resolution usually has to do with database forms or
views and programmers that want to have those views scale from one users
resolution to the next.  Even this is a silly thing to do by default.  Let
the user gain the ADVANTAGES he desires by running in the resolution he
desires.  A programmer steps out-of-line when he scales his application up
so when the user increases his resolution the he gains nothing because the
application adjusts and is just as big as it was at the lower resolution.


Maybe I'm misunderstanding your problem, if so clarify away.  But I'd sure
like to know what other piece of software you've encountered that's lead you
to believe this is something to worry about.



Regards,

------------------------------------------------------------------------
 Jim Burns, <mailto:[EMAIL PROTECTED]>
   Technology Dynamics
   Pearland, Texas  USA 
   281 485-0410 / 281 813-6939


_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi


_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi

Reply via email to