| adding a child to a child [message #192902] |
Tue, 23 August 2005 16:46  |
Eclipse User |
|
|
|
Originally posted by: pbeagan.yahoo_dontspamme_.com
I have EditParts A, B, C. B and C can both be children of A. C can also
be a child of B.
It seems that the Policy invoked when I try to drop C onto B is always that
of A. I installed a CONTAINER_ROLE edit policy for B, the behavior always
picks up the edit policy for A. Disabling A's CONTAINER_ROLE edit policy
and I can't drop anything on it.
I think I may need to use EditPartViewer.findEditPartAt(Point) but not sure
and looking for an example.
|
|
|
|
| Re: adding a child to a child [message #192961 is a reply to message #192930] |
Tue, 23 August 2005 21:06  |
| Eclipse User |
|
|
|
Originally posted by: pbeagan.yahoo_dontspamme_.com
They are both selectable, I can do things like direct-edit B or transfer B
to another A object.
My question is this: Should I be able to perform the behavior described in
my original post? Or do I need start looking into modifying a tool or
something to get the child object to pick up the CREATE request instead of
the parent?
Thanks-Patrick
Felix L J Mayer wrote:
> Are there any other differences between A and B? Like, are they both
> selectable etc?
>
> "Patrick" <pbeagan@yahoo_dontspamme_.com> wrote in message
> news:defjin$n9o$1@news.eclipse.org...
>>I have EditParts A, B, C. B and C can both be children of A. C can also
>> be a child of B.
>>
>> It seems that the Policy invoked when I try to drop C onto B is always
>> that
>> of A. I installed a CONTAINER_ROLE edit policy for B, the behavior
>> always
>> picks up the edit policy for A. Disabling A's CONTAINER_ROLE edit policy
>> and I can't drop anything on it.
>>
>> I think I may need to use EditPartViewer.findEditPartAt(Point) but not
>> sure
>> and looking for an example.
|
|
|
| Re: adding a child to a child [message #193005 is a reply to message #192961] |
Wed, 24 August 2005 03:55 |
| Eclipse User |
|
|
|
Originally posted by: none.unknown.com
Yes, it's possible. In the logic example, you can add the flow container to
a circuit and then add a part to that flow container. Does B have a
LayoutEditPolicy installed?
"Patrick" <pbeagan@yahoo_dontspamme_.com> wrote in message
news:deg2qj$b9p$1@news.eclipse.org...
> They are both selectable, I can do things like direct-edit B or transfer B
> to another A object.
>
> My question is this: Should I be able to perform the behavior described
in
> my original post? Or do I need start looking into modifying a tool or
> something to get the child object to pick up the CREATE request instead of
> the parent?
>
> Thanks-Patrick
>
>
>
> Felix L J Mayer wrote:
>
> > Are there any other differences between A and B? Like, are they both
> > selectable etc?
> >
> > "Patrick" <pbeagan@yahoo_dontspamme_.com> wrote in message
> > news:defjin$n9o$1@news.eclipse.org...
> >>I have EditParts A, B, C. B and C can both be children of A. C can
also
> >> be a child of B.
> >>
> >> It seems that the Policy invoked when I try to drop C onto B is always
> >> that
> >> of A. I installed a CONTAINER_ROLE edit policy for B, the behavior
> >> always
> >> picks up the edit policy for A. Disabling A's CONTAINER_ROLE edit
policy
> >> and I can't drop anything on it.
> >>
> >> I think I may need to use EditPartViewer.findEditPartAt(Point) but not
> >> sure
> >> and looking for an example.
>
|
|
|
| Re: adding a child to a child [message #193141 is a reply to message #193005] |
Wed, 24 August 2005 16:10 |
| Eclipse User |
|
|
|
Originally posted by: pbeagan.yahoo_dontspamme_.com
That was exactly what I was missing. B needed a layout policy.
Thanks!
Pratik Shah wrote:
> Yes, it's possible. In the logic example, you can add the flow container
> to
> a circuit and then add a part to that flow container. Does B have a
> LayoutEditPolicy installed?
>
> "Patrick" <pbeagan@yahoo_dontspamme_.com> wrote in message
> news:deg2qj$b9p$1@news.eclipse.org...
>> They are both selectable, I can do things like direct-edit B or transfer
>> B to another A object.
>>
>> My question is this: Should I be able to perform the behavior described
> in
>> my original post? Or do I need start looking into modifying a tool or
>> something to get the child object to pick up the CREATE request instead
>> of the parent?
>>
>> Thanks-Patrick
>>
>>
>>
>> Felix L J Mayer wrote:
>>
>> > Are there any other differences between A and B? Like, are they both
>> > selectable etc?
>> >
>> > "Patrick" <pbeagan@yahoo_dontspamme_.com> wrote in message
>> > news:defjin$n9o$1@news.eclipse.org...
>> >>I have EditParts A, B, C. B and C can both be children of A. C can
> also
>> >> be a child of B.
>> >>
>> >> It seems that the Policy invoked when I try to drop C onto B is always
>> >> that
>> >> of A. I installed a CONTAINER_ROLE edit policy for B, the behavior
>> >> always
>> >> picks up the edit policy for A. Disabling A's CONTAINER_ROLE edit
> policy
>> >> and I can't drop anything on it.
>> >>
>> >> I think I may need to use EditPartViewer.findEditPartAt(Point) but not
>> >> sure
>> >> and looking for an example.
>>
|
|
|
Powered by
FUDForum. Page generated in 0.03054 seconds
] 
Search
Help
Register
Login
Home
