Ignacio,
Your answers were just fine...I will study the sample a little more...
Thanks.
Regards
Aguiar !!!
"Ignacio Ortiz de Zúñiga" <
NoName@xailer.com> escreveu na mensagem
news:449ab8fc$[email=
1@ozsrvnegro.ozlan.local...]
1@ozsrvnegro.ozlan.local...[/email]
> Aguiar,
>
> That is the project we showed in Xailer free technical journeys and it
> uses some complex programming techniques that is difficult to explain on a
> few lines. It took more than 8 hours to see the all project. BTW I try to
> give you some clues, but you should learn through code I am afraid.
>
>> 1 - TFormFolder is a class to add a form to a folder, or to have a form
>> as folderpage. Right ?
>
> This is part of the new form inheritance. TFormFolder ia a inherited class
> from TFolderPage, that's all. When you indicate that your form inherits
> from it is just saying that it will be a FolderPage on runtime rather than
> a Form.
>
>> 2 - Is this class a generic to use with other applications ?
>
> Yes. Just add the TFormFolder to any of your projects.
>
>> 3 - To just add a form to a folder, methods New() and Create() from
>> TFormFolder are sufficient. Right ?
>
> Yes. Take a look at the code on Main form:
>
> ::oTabFac := TFrmFacturas():New( ::oFolder1 )
>
>> 4 - Are InsertComponent() and RemoveComponent() methods of XFolderPage ?
>> When are they called ? Is there some documantation about them ?
>
> No, they are internal and internally called. You should not concern about
> them.
>
>> 5 - How did you created those classes that comes from TFormfolder (like
>> TFrmClientes)? That's a regular form that you changed the "From" part
>> directly in the code ? Right ?
>
> Is just a regular form. And yes we just change the "From" part directly in
> the code.
>
>> 6 - In method New() from TFormFolder why do you call ::Createform() if it
>> is Virtual (i thought a virtual method does nothing...what does Virtual
>> means?)
>
> Inheritance magic

. CreateForm() is defined on lower classes like
> TFrmClientes and it is the responsable of controls creation. We prototype
> as VIRTUAL just to indicate that this class must be deployed by its child
> classes. Is just a good programming practice.
>
> Regards,
>
>
>