Board index » delphi » Inherited forms sized differently at run time than design time
Matt P
![]() Delphi Developer |
Thu, 06 Mar 2003 03:00:00 GMT
|
Matt P
![]() Delphi Developer |
Thu, 06 Mar 2003 03:00:00 GMT
Inherited forms sized differently at run time than design time
Hi,
I'm making heavy use of visual form inheritance, and I've just encountered a {*word*193} problem. I have a base dialog form with OK and Cancel buttons anchored to the -- Matt Palmer |
Paul Gallaghe
![]() Delphi Developer |
Thu, 06 Mar 2003 03:00:00 GMT
Re:Inherited forms sized differently at run time than design timeI don't know why your forms are a different size than inherited. Perhaps you changed their size at design time? If so, go into text view(alt+f12) of the form, and delete the height and width entries. When you place buttons on a form, you should always place them on a panel. Paul Gallagher Quote"Matt P" <matt.pal...@{*word*269}.net> wrote in message news:39c495f3_2@dnews... |
Matt
![]() Delphi Developer |
Thu, 06 Mar 2003 03:00:00 GMT
Re:Inherited forms sized differently at run time than design timeHmmm. The problem isn't that the forms are a different size than inherited. All the forms are sized individually. The problem is that the part of the form which *is* inherited, ie, the The forms were originally designed with scaling on, and I later realised Here's how it looks: Base form at design time: +-----------------------------------------+ Inherited form at design time: +-----------------------------------------+ Inherited form at runtime: +-----------------------------------------+ -- Matt Palmer QuotePaul Gallagher <p...@tansit.com> wrote in message Quote> I don't know why your forms are a different size than inherited. Perhaps Quote> > Hi, |
Michael Broomhea
![]() Delphi Developer |
Fri, 07 Mar 2003 03:00:00 GMT
Re:Inherited forms sized differently at run time than design timeSorry, no solution, but I have had the same problem with my MDI application, while my SDI application was OK. (I've been testing both MDI and SDI for the same application, just to see which one would be preferable). Maybe some resizing is done of the childs in an MDI application ? Michael QuoteMatt P wrote: |
Andrey Adamovic
![]() Delphi Developer |
Fri, 07 Mar 2003 03:00:00 GMT
Re:Inherited forms sized differently at run time than design timeIf your forms have BorderStyle: bsToolWindow or bsSizeableToolWindow, then the size of form differs at runtime and designtime, because the size of forms' caption is different. Form sets its Height to the Height specified at designtime, but it doesn't pay attention to the changing of caption size. I think it is a bug of Delphi or Windows, Anyway the solution may be to make your form's height less at design time... If you are using different BorderStyle, I can't really imagine what the problem could be... CU QuoteMatt P wrote: |
Matt
![]() Delphi Developer |
Fri, 07 Mar 2003 03:00:00 GMT
Re:Inherited forms sized differently at run time than design timeNope. Borderstyle is a normal default borderstyle on all forms. Changing the form size at design time of either the base form or the inherited forms makes *absolutely no difference* to the extra space which appears at the bottom of the form at runtime. This is the problem - the form is acquiring space which just doesn't appear at design time, no matter what I do. I can cure the problem by moving the OK and Cancel buttons almost off the edge of the form at design time. They then appear in roughly the correct position at runtime. So the controls anchor to the form as if they are{*word*154} off the form, but then the form acquires some extra height, so all is well... very strange. But this isn't a solution; it's a kludge to get around a bug in the way Matt Quote"Andrey Adamovich" <adamov...@solcraft.lv> wrote in message Quote> If your forms have BorderStyle: bsToolWindow or bsSizeableToolWindow, |
taine gillia
![]() Delphi Developer |
Fri, 07 Mar 2003 03:00:00 GMT
Re:Inherited forms sized differently at run time than design timeI've had a number of problems with MDI children not being created at designed size. For me the most stable Position choice was "poDefaultPosOnly". "poDesigned" was not at all what I expected. Of course, as pretty much everyone around here tells me there are quite a few flaws in MDI - both from MicroSoft and in the VCL. |
1. Q: Form.Width. design time versus run time
2. Form design/run-time size (bug???)
3. Form Size: different at design and run time
4. query runs at design time but not run time
5. Need components on an inherited form at design time
6. How to find out if Design-time or Run-time
7. Component - Design Time Great...Run-Time Not...Help
8. ???----Design Time and Run time