That appears to be the only way to do this since Delphi doesn't let me link a form with a different name to a .pas file in the project. Too bad really.
Thanks. John Wireless CAN with the CANRF module now available. http://www.autoartisans.com/products Automation Artisans Inc. Ph. 1 250 544 4950 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Marcin Bury > Sent: Wednesday, February 22, 2006 11:28 PM > To: Borland's Delphi Discussion List > Subject: Re: Using alternate forms with units. > > > John > > if only screen resolution matters I would think about > additional procedure that > will check the screen resolution on form creation as set all > neccessary object > properties. On resize event is very helpfull as well - I use > it almost on every > form positioning and resizing some form objects. > > HTH > Marcin > > ----- Original Message ----- > From: "John Dammeyer" <[EMAIL PROTECTED]> > To: "'Borland's Delphi Discussion List'" <[email protected]> > Sent: Thursday, February 23, 2006 4:00 AM > Subject: Using alternate forms with units. > > > > (Changed text to .dfm from .frm. What was I thinking.) > > > > Hi guys, > > > > I have an application that is targeted at two different > embedded systems > > using two different size LCD displays. When the initial project was > > expanded to the second larger display 1024x768 from 640x480 > the client also > > wanted a number of additions. > > > > Now I'm faced with the chore of taking what has become a > twin development > > stream and bringing it back into 1 since all the neat > features of the larger > > system are also wanted on the smaller. > > > > About 90% of the changes are object.width, .height, .left > and .top and also > > some font sizes. > > > > There are a few that are WIN98 specific verses WINXP or > WINNT but they are > > less of a problem with flags kept in the registry to > determine personality. > > > > To determine what the new positions and sizes should be the > easiest way was > > to copy the .frm file and just re-arrange until I liked > what I saw. Any of > > the graphical code that depends on the width or height of > the graphic can be > > dealt with using {$IFDEF} etc. > > > > What I'd like to be able to do is have PlotScreen.frm become > > PlotScreenBIG.dfm and PlotScreenSMALL.dfm but keep the > PlotScreen.pas file > > name. Is there a way to convince Delpi 5 to use a .dfm > file different from > > the name of the unit during compilation. Then I could just... > > > > {$IFDEF LARGE_SCREEN} > > ... Somehow use PlotScreenBIG.dfm > > {$ELSE} > > ... Somehow use PlotScreenSMALL.dfm > > {$ENDIF} > > > > Thanks, > > > > John Dammeyer > > > > > > > > Wireless CAN with the CANRF module now available. > > http://www.autoartisans.com/products > > Automation Artisans Inc. > > Ph. 1 250 544 4950 > > > > _______________________________________________ > > Delphi mailing list -> [email protected] > > http://www.elists.org/mailman/listinfo/delphi > > > > _______________________________________________ > Delphi mailing list -> [email protected] > http://www.elists.org/mailman/listinfo/delphi > > _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
