<div>
Are you using borland delphi IDE?
</div>


<div>
If not you can get installer here: <br />
<a href="http://www.brothersoft.com/downloads/borland-delphi.html" rel="ugc">http://www.brothersoft.com/downloads/borland-delphi.html</a><br />
<br />

</div>


<div>
Yes, I am using BDS 2006 Enterprise version. 
</div>


<div>
After you create a form, you can go to tool palette and select the component you want.<br />
Here you want Tedit then you go to tool palette and select Tedit by left click.<br />
in you form you left click then the component will appear on the form.<br />
to change the setting or property on the Tedit just go to object inspector on your right hand side.<br />
<br />
you can also change property via code<br />
procedure TForm1.Button1Click(Sender<wbr />: TObject);<br />
begin<br />
edit1.color := clblue;<br />
end;<br />

</div>


<div>
Thank you Geert. I did gather that what I needed was quite advanced though I have designed &nbsp;simpler objects before. I will study the code you posted. I realized that I could osrt of accomplish what I want using form inheritance and instead of needing a collection of edits I could just drop edits onto the forms. But our current project has several custom tframes and they currently have a bunch of tedits (hidden out of view). The dits are only brought into view if the particular part of the app needs them. i was hoping to have a neater way of doing this, so my concept was to have a class that was a collection of edits and I would only create the edits at design time as needed.
</div>


<div>
Actually you already have a collection of TEdits...if they are hidden on a frame...<br />
<br />
The Frame has a property called Controls. &nbsp;It's a list of Controls that list this control as it's Parent.<br />
<br />
You can iterate through the list easily...and find the control your looking for...<br />
<br />
<br />

<pre><code class="code-10 nolinks" id="code-265351"><span></span>
<span>function FindEditControl(aWinControl: TWinControl; aName: string): TEdit;</span>
<span>var</span>
<span>  a_Index: integer;</span>
<span>begin</span>
<span>  Result := nil;</span>
<span>  for a_Index := 0 to aWinControl.ControlCount - 1 do</span>
<span>  begin</span>
<span>    if (aWinControl.Controls[a_Index] is TEdit) and</span>
<span>       (aWinControl.Controls[a_Index].Name = aName)then</span>
<span>    begin</span>
<span>      Result := TEdit(aWinControl.Controls[a_Index]);</span>
<span>    end;</span>
<span>  end;</span>
<span> </span>
<span>end;</span>
<span> </span>
<span>procedure TForm1.Button1Click(Sender: TObject);</span>
<span>begin</span>
<span>  FindEditControl(Form1, Edit2.Name).Text := 'Here';</span>
<span>end;</span>
</code></pre>
</div>


<div>
Ah but if I turn the frame into a template (Add to Palette), I can drop as many of the frames onto a form as I want but can no longer create text edits in them via the designer which is why my solution was to create as many tedits in the frame as I thought I might need, and just hide them until they're needed. I know it's not the best way to do things, but using frames this way allows me to create the objects visually and they have been working well for my little shop for quite some time.
</div>


<div>
create as many edits , and just hide them ...<br />
<br />
and why not create them as needed ?<br />
what is the interface like ?<br />
wild guess: the frame should edit a database table record ?<br />
and each column would be a edit ?<br />

</div>


<div>
Hmm...still don't understand the problem with my approach...<br />
<br />
You get to keep the system the way you have it currently designed. &nbsp;Frames designed with TEdits dropped on it during design and hidden from view until needed.<br />
<br />
The code same I gave above works with Frames...<br />
<br />
<br />

<pre><code class="code-10 nolinks" id="code-266010"><span>procedure TForm1.Button1Click(Sender: TObject);</span>
<span>var</span>
<span>  a_Edit: TEdit;</span>
<span>begin</span>
<span>  a_Edit := FindEditControl(Frame1, 'Edit2');</span>
<span>  if Assigned(a_Edit) then</span>
<span>  begin</span>
<span>    a_Edit.Visible := True;</span>
<span>    a_Edit.Text := 'Here';</span>
<span>  end;</span>
<span>end;</span>
</code></pre>
</div>


<div>
Thanks to both of you for continuing to comment. <br />
<br />
Yes, the frame is designed for database use. I don't create the edit as needed because I don't create objects in code - I always design visually. I guess in this respect, I would be better off using form inheritance and embedded forms as unlike the frames, they would allow me to add whatever components I need at design time. <br />
<br />
I know how to access the components on a form or a frame programmatically as in Dexter's code. I was sort of hoping for a more neat way of having the frame allow me to create and configure x TEdits (or tlabels or some other control) where x is only known at design time, in similar fashion to the way peristent columns are created in a tdbgrid. <br />
<br />
I was thinking that the likely way to implement this would be to use a tcollection, while examining the code for Borland's TButtonGroup, I thought I would find that the Button Collection would be a collection of TButtons. Instead, I realized that the buttons in a button group are actually a custom object descended from TCollectionItem as that is what a collection must consist of. I was hoping there was some other way of doing this other than creating a TCollectionItem descendant that was in all other respects a Tedit.
</div>


<div>
in the long run, you could create yourself a wizard like the one provided in the menu / Database / Form wizard
</div>


<div>
<div class="content wysiwyg-content">
My background in Pascal is mostly procedural. I have created a non-visual component and I would like to add to it a property, Edits, which would be a collection of Text Edits (tedit) that are placed on the frame of the non-visual component as they are created. The behavior I am going for is something like the way status bar panels work: (I drop a status bar, right-click to access the panels editor and from there I am able to create as many panels as I need) I would like to be able to drop my component on a frame or a form and right-click on it to create as many tedits as I care to create.<br />
<br />
I have no idea how to do this, though.
</div>
</div>


My background in Pascal is mostly procedural. I have created a non-visual component and I would like to add to it a property, Edits, which would be a collection of Text Edits (tedit) that are placed on the frame of the non-visual component as they are created. The behavior I am going for is something like the way status bar panels work: (I drop a status bar, right-click to access the panels editor and from there I am able to create as many panels as I need) I would like to be able to drop my component on a frame or a form and right-click on it to create as many tedits as I care to create.

I have no idea how to do this, though.

How do I create a collection of tedits in Delphi?

Delphi is the most powerful Object Pascal IDE and component library for cross-platform Native App Development with flexible Cloud services and broad IoT connectivity. It provides powerful VCL controls for Windows 10 and enables FMX development for Windows, Mac and Mobile. Delphi is your choice for ultrafast Enterprise Strong Development™. Look for increased memory for large projects, extended multi-monitor support, improved Object Inspector and much more. Delphi is 5x faster for development and deployment across multiple desktop, mobile, cloud and database platforms including 32-bit and 64-bit Windows 10.