{"id":119,"date":"2007-05-12T14:33:50","date_gmt":"2007-05-12T12:33:50","guid":{"rendered":" http:\/\/www.nsonic.de\/blog\/2007\/05\/small-fonts-large-fonts-2-formscaler\/"},"modified":"2007-05-12T14:33:52","modified_gmt":"2007-05-12T12:33:52","slug":"small-fonts-large-fonts-2-formscaler","status":"publish","type":"post","link":"https:\/\/www.nsonic.de\/blog\/2007\/05\/small-fonts-large-fonts-2-formscaler\/","title":{"rendered":"Small Fonts \/ Large Fonts (2) – FormScaler"},"content":{"rendered":"

In article <3aaefd89_2@dnews>, William Meyer wrote:<\/p>\n

> Small fonts\/large fonts is a problem without a clean solution. The
\n> suggestion will be to develop at large fonts, and the result will work ok on
\n> small fonts, but it looks funny to me. I’ve toyed with actually designing
\n> two sets of forms, and loading them based on the font set in use at runtime.
\n<\/em>
\nI develop with small fonts and ‘Scaled’ set to false. When I’m doing
\ndialog-box style forms I drop a TFormScaler component on the form. It seems
\nto work…<\/p>\n

Here’s TFormScaler – it’s quite simple!
\n
\nfile:\/\/———————————————————————
\n[code lang=”delphi”]unit cmpFormScaler;<\/p>\n

interface<\/p>\n

uses
\n Windows, Messages, SysUtils, Classes, Graphics, Controls, Forms, Dialogs;<\/p>\n

type
\n TFormScaler = class(TComponent)
\n private
\n fScaled : Boolean;
\n fDivisor : Integer;
\n fMultiplier : Integer;
\n protected
\n procedure Loaded; override;
\n public
\n property M : Integer read fMultiplier;
\n property D : Integer read fDivisor;
\n { Public declarations }
\n published
\n { Published declarations }
\n end;<\/p>\n

implementation<\/p>\n

const
\n SmallFontsI = 454;<\/p>\n

{ TFormScaler }<\/p>\n

procedure TFormScaler.Loaded;
\nvar
\n frm : TForm;
\n s : string;
\n c : TCanvas;
\nbegin
\n inherited;
\n if not (csDesigning in ComponentState) and not fScaled then
\n begin
\n fScaled := True;
\n if Owner is TForm then
\n begin
\n frm := TForm (Owner);
\n frm.Scaled := False;<\/p>\n

c := TCanvas.Create;
\n c.Handle := GetDC (HWND_DESKTOP);<\/p>\n

try
\n s :=
\n‘ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz1234567890-=+_)(*&^%$\u00a3”!’
\n;
\n fMultiplier := c.TextWidth (s);<\/p>\n

fDivisor := SmallFontsI;
\n frm.ScaleBy (fMultiplier, fDivisor);
\n finally
\n ReleaseDC (HWND_DESKTOP, c.Handle);
\n c.Free
\n end
\n end
\n end
\nend;<\/p>\n

end.
\n[\/code]<\/p>\n

[tags]Delphi, Forms[\/tags]<\/p>\n","protected":false},"excerpt":{"rendered":"

In article <3aaefd89_2@dnews>, William Meyer wrote: > Small fonts\/large fonts is a problem without a clean solution. The > suggestion will be to…<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":""},"categories":[11],"tags":[75,100],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p71Tml-1V","_links":{"self":[{"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/posts\/119"}],"collection":[{"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/comments?post=119"}],"version-history":[{"count":0,"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/posts\/119\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/media?parent=119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/categories?post=119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.nsonic.de\/blog\/wp-json\/wp\/v2\/tags?post=119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}