如何根据显示器的大小，定义不同大小的form(100分)

创建窗体时读一下注册表不就知道了吗?
如果不知道怎么读注册表去看一下TRegisty(好像是这样拼的)
的帮助,我忘了

Give you some tips

1.Form Sizes on different platforms

Question

I am trying to make my app work on screen sizes eg. 640x480 &
1024x768 I have tried changing the pixels per inch property but
it doesn't seem to work.

Answer

A:
The following should help make your forms look correct at different
resolutions:
a.) Set Autoscroll to' FALSE'. True means don't change the form's frame size
at run time.
b.) Set the font to a TrueType like Arial, don't leave it at the default
'SYSTEM''
c.) Set Position to something other than poDesigned, this will leave it where
you left it on your 1280x780 screen which maybe barely visible at 640x480.
d.) Change Pitch property of the font from DEFAULT to VARIABLE
e.) DON'T CHANGE THE PixelsPerInch PROPERTY.
f.) Set the Scaled Property to TRUE. This scales the forms to the value of
the PixelsPerInch property.

Screen resolution

Question

Has anyone else noticed that your Delphi app looks wonderful on YOUR
windows setup, but gets screwed up on others?

Answer

A:
Here is an exerpt from Lloyd's Help File

==================================================

Screen Resolution

When designing forms, it is sometimes helpful to write the code so
that the screen and all of its objects are displayed at the same size
no matter what the screen resolution is. Here is some code to show
how that is done:

implementation
const
ScreenWidth: LongInt = 800; {I designed my form in 800x600 mode.}
ScreenHeight: LongInt = 600;

{$R *.DFM}

procedure TForm1.FormCreate(Sender: TObject);
begin
scaled := true;
if (screen.width <> ScreenWidth) then

begin
height := longint(height) * longint(screen.height) DIV
ScreenHeight;
width := longint(width) * longint(screen.width) DIV ScreenWidth;
scaleBy(screen.width, ScreenWidth);
end;
end;


Then, you will want to have something that checks to see that the
font sizes are OK. Before you change the font's size, you would need
to ensure the object actually has a font property by checking the
RTTI. This can be done as follows:


USES typinfo; {Add this to your USES statement.}

var
i: integer;
begin
for i := componentCount - 1 downto 0 do
with components do
begin
if GetPropInfo(ClassInfo, 'font') <> nil then
font.size := (NewFormWidth DIV OldFormWidth) * font.size;
end;
end;

{This is the long way to do the same thing.}
var
i: integer;
p: PPropInfo;
begin
for i := componentCount - 1 downto 0 do
with components do

begin
p := GetPropInfo(ClassInfo, 'font');
if assigned(p) then
font.size := (NewFormWidth DIV OldFormWidth) * font.size;
end;
end;


Note: not all objects have a FONT property. This should be enough
to get you started.

Note: The following are issue to bear in mind when scaling Delphi
applications (forms) on different screen resolutions:

* Decide early on in the form design stage whether you're going to
allow the form to be scaled or not. The advantage of not scaling is
that nothing changes at runtime. The disadvantage of not scaling is
that nothing changes at runtime (your form may be far too small or
too large to read on some systems if it is not scaled).

* If you're NOT going to scale the form, set Scaled to False.

* Otherwise, set the Form's Scaled property to True.

* Set AutoScroll to False. AutoScroll = True means 'don't change the
form's frame size at runtime' which doesn't look good when the
form's contents do change size.

* Set the form's font to a scaleable TrueType font, like Arial. MS
San Serif is an ok alternate, but remember that it is still a
bitmapped font. Only Arial will give you a font within a pixel of
the desired height. NOTE: If the font used in an application is not
installed on the target computer, then Windows will select an
alternative font within the same font family to use instead. This
font may not match the same size of the original font any may cause
problems.


* Set the form's Position property to something other than
poDesigned. poDesigned leaves the form where you left it at design
time, which for me always winds up way off to the left on my
1280x1024 screen - and completely off the 640x480 screen.

* Don't crowd controls on the form - leave at least 4 pixels between
controls, so that a one pixel change in border locations (due to
scaling) won't show up as ugly overlapping controls.

* For single line labels that are alLeft or alRight aligned, set
AutoSize to True. Otherwise, set AutoSize to False.


* Make sure there is enough blank space in a label component to allow
for font width changes - a blank space that is 25% of the length of
the current string display length is a little too much, but safe.
(You'll need at least 30% expansion space for string labels if you
plan to translate your app into other languages) If AutoSize is
False, make sure you actually set the label width appropriately. If
AutoSize is True, make sure there is enough room for the label to
grow on its own.

* In multi-line, word-wrapped labels, leave at least one line of
blank space at the bottom. You'll need this to catch the overflow
when the text wraps differently when the font width changes with
scaling. Don't assume that because you're using large fonts, you
don't have to allow for text overflow - somebody else's large fonts
may be larger than yours!

* Be careful about opening a project in the IDE at different
resolutions. The form's PixelsPerInch property will be modified as
soon as the form is opened, and will be saved to the DFM if you save
the project. It's best to test the app by running it standalone, and
edit the form at only one resolution. Editing at varying resolutions
and font sizes invites component drift and sizing problems.


* Speaking of component drift, don't rescale a form multiple times,
at design time or a runtime. Each rescaling introduces roundoff
errors which accumulate very quickly since coordinates are strictly
integral. As fractional amounts are truncated off control's origins
and sizes with each successive rescaling, the controls will appear
to creep northwest and get smaller. If you want to allow your users
to rescale the form any number of times, start with a freshly
loaded/created form before each scaling, so that scaling errors do
not accumulate.

* Don't change the PixelsPerInch property of the form, period.

* In general, it is not necessary to design forms at any particular
resolution, but it is crucial that you review their appearance at
640x480 with small fonts and large, and at a high-resolution with
small fonts and large before releasing your app. This should be
part of your regular system
compatibility testing checklist.

* Pay close attention to any components that are essentially
single-line TMemos - things like TDBLookupCombo. The Windows
multi-line edit control always shows only whole lines of text - if
the control is too short for its font, a TMemo will show nothing at
all (a TEdit will show clipped text). For such components, it's
better to make them a few pixels too large than to be one pixel too
small and show not text at all.


* Keep in mind that all scaling is proportional to the difference in
the font height between runtime and design time, NOT the pixel
resolution or screen size. Remember also that the origins of your
controls will be changed when the form is scaled - you can't very
well make components bigger without also moving them over a bit.





Screen Resolution

Question

When I run a program on my computer everything looks fine, but when I
run it on my other computer, with a higher screen resilotion it looks
totaly different. How can I get it to look the same in any resolution.

Answer

Borland's document ti2861 gave some mileage..and I give it to you with
some of my modifications..here is:

TI2861 - Form display with different screen resolutions.

Product: Delphi
Version: All
Platform: Windows/Win32

When designing forms, it is sometimes helpful to write the code
so that the screen and all of its objects are displayed at the
same size no matter what the screen resolution is. Here is
some code to show how that is done:

implementation
const
ScreenWidth: LongInt = 640; {I designed my form in 640x480 mode.}
ScreenHeight: LongInt = 480;

{$R *.DFM}

procedure TForm1.FormCreate(Sender: TObject);
begin
scaled := true;
if (screen.width <> ScreenWidth) then
begin
height := longint(height) * longint(screen.height) div ScreenHeight;
width := longint(width) * longint(screen.width) div ScreenWidth;
scaleBy(screen.width, ScreenWidth);
end;
end;

Then, you will want to have something that checks to see that
the font sizes are OK. You can iterate over each child
control's font to adjust its size as necessary. This can be
done as follows:

type
TFooClass = class(TControl); { needed to get at protected }
{ font property }

var
i,NewFormWidth,OldFormWidth : integer;
begin
NewFormWidth := GetsystemMetrics(0); <-- gives you your window's width
OldFormWidth := 640; <-- This is my resolution
for i := ControlCount - 1 downto 0 do
TFooClass(Controls).Font.Size :=
(NewFormWidth div OldFormWidth) *
TFooClass(Controls).Font.Size;
end;

This will calculate all your fonts, objects that are on your forms...

Note: The following are issue to bear in mind when scaling
Delphi applications (forms) on different screen resolutions:

* Decide early on in the form design stage whether you're
going to allow the form to be scaled or not. The advantage of
not scaling is that nothing changes at runtime. The
disadvantage of not scaling is that nothing changes at runtime
(your form may be far too small or too large to read on some
systems if it is not scaled).


* If you're NOT going to scale the form, set Scaled to False.

* Otherwise, set the Form's Scaled property to True.

* Set AutoScroll to False. AutoScroll = True means 'don't
change the form's frame size at runtime' which doesn't look
good when the form's contents do change size.

* Set the form's font to a scaleable TrueType font, like
Arial. MS San Serif is an ok alternate, but remember that it
is still a bitmapped font. Only Arial will give you a font
within a pixel of the desired height. NOTE: If the font used
in an application is not installed on the target computer, then
Windows will select an alternative font within the same font
family to use instead. This font may not match the same size
of the original font any may cause problems.

* Set the form's Position property to something other than
poDesigned. poDesigned leaves the form where you left it at
design time, which for me always winds up way off to the left
on my 1280x1024 screen - and completely off the 640x480 screen.

* Don't crowd controls on the form - leave at least 4 pixels
between controls, so that a one pixel change in border
locations (due to scaling) won't show up as ugly overlapping
controls.

* For single line labels that are alLeft or alRight aligned,
set AutoSize to True. Otherwise, set AutoSize to False.

* Make sure there is enough blank space in a label component
to allow for font width changes - a blank space that is 25% of
the length of the current string display length is a little too
much, but safe. (You'll need at least 30% expansion space for
string labels if you plan to translate your app into other
languages) If AutoSize is False, make sure you actually set
the label width appropriately. If AutoSize is True, make sure
there is enough room for the label to grow on its own.

* In multi-line, word-wrapped labels, leave at least one line
of blank space at the bottom. You'll need this to catch the
overflow when the text wraps differently when the font width
changes with scaling. Don't assume that because you're using
large fonts, you don't have to allow for text overflow -
somebody else's large fonts may be larger than yours!

* Be careful about opening a project in the IDE at different
resolutions. The form's PixelsPerInch property will be
modified as soon as the form is opened, and will be saved to
the DFM if you save the project. It's best to test the app by
running it standalone, and edit the form at only one
resolution. Editing at varying resolutions and font sizes
invites component drift and sizing problems.

* Speaking of component drift, don't rescale a form multiple
times, at design time or a runtime. Each rescaling introduces
roundoff errors which accumulate very quickly since coordinates
are strictly integral. As fractional amounts are truncated
off control's origins and sizes with each successive
rescaling, the controls will appear to creep northwest and get
smaller. If you want to allow your users to rescale the form
any number of times, start with a freshly loaded/created form
before each scaling, so that scaling errors do not accumulate.

* Don't change the PixelsPerInch property of the form, period.

* In general, it is not necessary to design forms at any
particular resolution, but it is crucial that you review their
appearance at 640x480 with small fonts and large, and at a
high-resolution with small fonts and large before releasing
your app. This should be part of your regular system
compatibility testing checklist.

* Pay close attention to any components that are essentially
single-line TMemos - things like TDBLookupCombo. The Windows
multi-line edit control always shows only whole lines of text
- if the control is too short for its font, a TMemo will show
nothing at all (a TEdit will show clipped text). For such
components, it's better to make them a few pixels too large
than to be one pixel too small and show not text at all.

* Keep in mind that all scaling is proportional to the
difference in the font height between runtime and design time,
NOT the pixel resolution or screen size. Remember also that
the origins of your controls will be changed when the form is
scaled - you can't very well make components bigger without
also moving them over a bit.

to 小猪:
screen.width
screen.height

need not 注册表

to xsoftbox:
是否为按比例的form?

Tform1.formshow
self.width:=round(screen.width*self.width/1280);
self.height:=round(screen.height*self.width/1024);

....

从注册表中可以获得，但是如果根据不同的显示器大小来定义不同的form，是否有一定的牵强
性，如果有人拿17的显示器用640*480看东西的话，而你画一个1024*768的form，如果超出屏幕
的范围该如何办。所以提议，应该根据分辨率的大小进行定义不同的form更为合理。
分辨率很好获得。

英文真头痛
to :jqw
self.可以不要的,写起来太繁
谢谢提醒,哎,老了,老了...

还是根据分辩率来确定 form的大小吧。

我有一个formAutoSize的控件,但是还没有用过,如果需要告诉我你的mail.

to freefly:
give me one,ok?

jiangqw@263.net

这个问题我也遇到过但是再其他delphi站点找到过相应的中文说明我在网吧不便提供原代码
可以再找找看。也可以买一个delphi大本营的道版光盘里面也有介绍

to 小猪:
I am sorry

接受答案了.