Owner vs Parent vs ParentForm

[Tom W]

What's the difference in these three?

[Cor Ligthert [MVP]]

Tom,

I don't have anything specific in mind beyond what Owner offers, but I
didn't understand why Parent and ParentForm were available on the form
class.

As Jay stated, forms inherits from controls, because of that you will see
all methods, events and properties from Control. That does not mean they are
usefull. There are which are complete unusable. By instance the
backgroundimage in a textbox.

I hope this gives some more ideas

Cor

[Tom W]

Good enough. Thanks

Tom

Cor Ligthert [MVP] wrote:

Tom,

I don't have anything specific in mind beyond what Owner offers, but I
didn't understand why Parent and ParentForm were available on the form
class.

As Jay stated, forms inherits from controls, because of that you will see
all methods, events and properties from Control. That does not mean they are
usefull. There are which are complete unusable. By instance the
backgroundimage in a textbox.

I hope this gives some more ideas

Cor

[Jay B. Harlow [MVP - Outlook]]

Tom,
As Cor & I stated. Form inherits from Control. Which means that Form has all
the properties & methods that Control has. This can be very useful,
especially when you use a Form as a Control, in which case you need those
properties. However when using a Form as a Form, then those properties may
or may not be that useful.

Hope this helps
Jay

"Tom W" <di**********@n ospam.com> wrote in message
news:uu******** ******@TK2MSFTN GP09.phx.gbl...
|I don't have anything specific in mind beyond what Owner offers, but I
| didn't understand why Parent and ParentForm were available on the form
| class.
|
| Jay B. Harlow [MVP - Outlook] wrote:
| > Tom,
| > Parent is a Control to Control relationship.
| >
| > ParentForm is a Control to Form relationship.
| >
| > I really don't see how you would see a Form to Form relationship in
either
| > Parent or ParentForm, unless you placed one Form as Child *Control* of a
| > second Form. Then however your "Form" is no longer a Form, but its now a
| > Control!
| >
| > What specifically do you have in mind?
| >
| > Hope this helps
| > Jay
| >
| > "Tom W" <di**********@n ospam.com> wrote in message
| > news:uz******** ******@TK2MSFTN GP09.phx.gbl...
| > | OK great, owner provides functionality that ties forms togther when
| > | minimizing and maximizing. But you can reference Parent and ParentForm
| > | from a form class. Can that just be used as another way to tie them
| > | together that doesn't provide any functionality?
| > |
| > | Tom
| > |
| > | Jay B. Harlow [MVP - Outlook] wrote:
| > | > Tom,
| > | > | What's the difference in these three?
| > | > | Owner vs Parent vs ParentForm
| > | >
| > | > Form.Owner - Is the Form that "owns" this form. For example a
modless
| > | > Find/Replace dialog would be Owned by Notepad's main window. If you
| > minimize
| > | > the main Form, the owned form will minimize, if you restore the main
| > form,
| > | > the owned form will restore... Normally used for "tool" windows in
SDI
| > | > applications...
| > | >
| > | > Control.Parent - Is the immediate control that this control is
placed
| > on.
| > | > For example an option button placed in a Panel or GroupBox would
have
| > that
| > | > Panel or GroupBox as its Parent.
| > | >
| > | > ContainerContro l.ParentForm - is the Form that this ContainerContro l
is
| > | > ultimately placed on, however the Parent of the ContainerContro l
maybe
| > | > another ContainerContro l, which may have another Control as its
Parent,
| > | > which may then be a Form. Basically this does a Control.Parent until
it
| > | > finds a type that inherits from Form.
| > | >
| > | > Hope this helps
| > | > Jay
| > | >
| > | > "Tom W" <di**********@n ospam.com> wrote in message
| > | > news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
| > | > | What's the difference in these three?
| > | >
| > | >
| >
| >