How to know when a component is draged on a form?

[Mario Vázquez]

Hi all,
I'm trying to build a component which takes advantage of other components.
So, when this new component is draged to the form, I would like to insert
other components on the designer and relate them. But only the first time
the component is inserted! to avoid inserting components each time de form
is loaded in the IDE.
How can I hook the very first time a component is draged on a windows form?

Thanks for attention,
Mario Vazquez

[Carlos J. Quintero [VB MVP]]

Hi,

I was also interested in that problem and I found that the ComponentAdded
event does not provide that info. There are several cases:

- A component added from the toolbox
- A paste operation
- An undo operation (that places a control that was deleted)
- ...

Maybe a control designer has other hooks but the ComponentAdded event that
add-ins can use doesn't.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"Mario Vázquez" <al*****@micros oft.comescribió en el mensaje
news:%2******** ********@TK2MSF TNGP06.phx.gbl. ..

Hi all,
I'm trying to build a component which takes advantage of other components.
So, when this new component is draged to the form, I would like to insert
other components on the designer and relate them. But only the first time
the component is inserted! to avoid inserting components each time de form
is loaded in the IDE.
How can I hook the very first time a component is draged on a windows
form?

Thanks for attention,
Mario Vazquez

[Mario Vázquez]

Hi Carlos,

Thanks for the tip.
Well, it seems not an easy issue.
I've just found an interface (framework 2.0) that may help.
IComponentIniti alizer
It has two methods which give a choice to hook the creation of new and
existing components. But i've not investigate if this is true for all the
cases you expose.

Regards,
Mario Vazquez

"Carlos J. Quintero [VB MVP]" <no****@nospam. comescribió en el mensaje
news:eJ******** ******@TK2MSFTN GP06.phx.gbl...

Hi,

I was also interested in that problem and I found that the ComponentAdded
event does not provide that info. There are several cases:

- A component added from the toolbox
- A paste operation
- An undo operation (that places a control that was deleted)
- ...

Maybe a control designer has other hooks but the ComponentAdded event that
add-ins can use doesn't.

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"Mario Vázquez" <al*****@micros oft.comescribió en el mensaje
news:%2******** ********@TK2MSF TNGP06.phx.gbl. ..

>Hi all,
I'm trying to build a component which takes advantage of other
components. So, when this new component is draged to the form, I would
like to insert other components on the designer and relate them. But only
the first time the component is inserted! to avoid inserting components
each time de form is loaded in the IDE.
How can I hook the very first time a component is draged on a windows
form?

Thanks for attention,
Mario Vazquez

[Carlos J. Quintero [VB MVP]]

Ah, yes, I found that interface sometime ago but I don't know how to use it
from outside a control designer (from an add-in, for example). Let me know
if you get more info.
--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"Mario Vázquez" <al*****@micros oft.comescribió en el mensaje
news:ep******** ******@TK2MSFTN GP04.phx.gbl...

Hi Carlos,

Thanks for the tip.
Well, it seems not an easy issue.
I've just found an interface (framework 2.0) that may help.
IComponentIniti alizer
It has two methods which give a choice to hook the creation of new and
existing components. But i've not investigate if this is true for all the
cases you expose.

Regards,
Mario Vazquez

[Mario Vázquez]

Hi Carlos,

I still have'nt work with add-ins and macros, so I cannot properly talk
about it, but I'll explain you how I use this interface through the designer
of a component, and perhaps it helps you.
Anyway, I was testing the points you expose in your previous message, and
this interface does'nt solve them.

// Make the designer implements IComponentIniti alizer
class MyComponentDesi gner:System.Com ponentModel.Des ign.ComponentDe signer,
IComponentIniti alizer
{
...

// Implement the interface
void
IComponentIniti alizer.Initiali zeExistingCompo nent(System.Col lections.IDicti onary
defaultValues)
{
base.Initialize ExistingCompone nt(defaultValue s);
// hook point
}

void
IComponentIniti alizer.Initiali zeNewComponent( System.Collecti ons.IDictionary
defaultValues)
{
base.Initialize NewComponent(de faultValues);
// hook point }
}
}

"Carlos J. Quintero [VB MVP]" <no****@nospam. comescribió en el mensaje
news:ee******** ******@TK2MSFTN GP06.phx.gbl...

Ah, yes, I found that interface sometime ago but I don't know how to use
it from outside a control designer (from an add-in, for example). Let me
know if you get more info.
--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
"Mario Vázquez" <al*****@micros oft.comescribió en el mensaje
news:ep******** ******@TK2MSFTN GP04.phx.gbl...

>Hi Carlos,

Thanks for the tip.
Well, it seems not an easy issue.
I've just found an interface (framework 2.0) that may help.
IComponentInit ializer
It has two methods which give a choice to hook the creation of new and
existing components. But i've not investigate if this is true for all the
cases you expose.

Regards,
Mario Vazquez