Re: component nested in component
- From: "Bruce Roberts" <dontsendtober@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 31 Oct 2005 13:21:11 -0500
"Juergen" <juergenschlinker@xxxxxx> wrote in message
news:1130780011.331411.237050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I know, but in my case each button _has_ it's own Popupmenu so there is
> no need for me to have the popupmenu "outside" my component lying on
> the mainform.
So what you want to have is the popup menu Owned and Parented by your
component. You will then have to provide a mechanism in your component to
allow you to add / change non-common menu items. If every instance is going
to have non-common menu items, its probably much easier to simply live with
all the menu components appearing at design time. Just put them on-top of
each other, so they don't take up too much space.
.
- References:
- component nested in component
- From: Juergen
- Re: component nested in component
- From: Bruce Roberts
- Re: component nested in component
- From: Juergen
- Re: component nested in component
- From: Bruce Roberts
- Re: component nested in component
- From: Juergen
- component nested in component
- Prev by Date: Re: component nested in component
- Previous by thread: Re: component nested in component
- Next by thread: Problems with FindLast command.
- Index(es):