Re: TSplitter Persistence problem
- From: Rob Kennedy <me3@xxxxxxxxxxx>
- Date: Mon, 22 Aug 2005 16:22:27 -0500
samjones wrote:
Delphi returns this same sequence when the controls are positioned properly or with the problem positioning. Therefore I assume Delphi does not use the Controls array sequence to define the controls position in a container. In C#, Controls determines the position in the container and Controls.SetIndex
(Splitter1,1) would move Splitter1 to the second position in the container.
Are you using .Net? If you are, you should say so. Otherwise, most of us will assume you're using Win32. If you're using .Net, then the Controls property should work the same as it does in C# because C# and Delphi both get the property from the .Net Framework's class library. At least, a Delphi WinForms program should have the same behavior. A Delphi VCL program might have its own Controls array implemented the same as it is in the Win32 version of the VCL.
So how does Delphi determine the position of a control in a container?
By the order in which they are added to that container. When you drop controls on your form, descendants of TGraphicControl are placed ahead of descendants of TWinControl. There is a good reason for that. I can't think of what it is right now, though. Probably something to do with Z-ordering and a lack of window handles.
And more importantly how do we manipulate it?
Create the controls in a different order.
-- Rob .
- References:
- Re: TSplitter Persistence problem
- From: Maarten Wiltink
- Re: TSplitter Persistence problem
- From: samjones
- Re: TSplitter Persistence problem
- Prev by Date: Re: TSplitter Persistence problem
- Next by Date: Re: TSplitter Persistence problem
- Previous by thread: Re: TSplitter Persistence problem
- Next by thread: Re: TSplitter Persistence problem
- Index(es):
Relevant Pages
|