| Prevent Child Selection with policy? [message #97509] |
Mon, 06 October 2003 20:52  |
Eclipse User |
|
|
|
Originally posted by: ThisisFake.Fakeness.xyz
I have a component that contains other parts. I prevent its children from
being selected if I drag a box around this compomnent, or a box that just
contains its children by returning false to isSelectable if this
components parents parent is not a RootEditPart.
Is this the architecturally correct way to do this? Is their a selection
policy or anything for the container? Anyway I can use a policy for this?
Carl
|
|
|
| Re: Prevent Child Selection with policy? [message #97549 is a reply to message #97509] |
Tue, 07 October 2003 01:30  |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
Is this related to "grouping" above?
"CL [dnoyeB] Gilbert" <ThisisFake@Fakeness.xyz> wrote in message
news:pan.2003.10.06.20.52.22.823555@Fakeness.xyz...
> I have a component that contains other parts. I prevent its children from
> being selected if I drag a box around this compomnent, or a box that just
> contains its children by returning false to isSelectable if this
> components parents parent is not a RootEditPart.
>
> Is this the architecturally correct way to do this? Is their a selection
> policy or anything for the container? Anyway I can use a policy for this?
>
>
>
> Carl
|
|
|
| Re: Prevent Child Selection with policy? [message #97618 is a reply to message #97549] |
Tue, 07 October 2003 02:23 |
| Eclipse User |
|
|
|
Originally posted by: ThisisFake.Fakeness.xyz
On Mon, 06 Oct 2003 21:30:42 -0400, Randy Hudson wrote:
> Is this related to "grouping" above?
>
Well it wasn't. This was my first method. where you basically have a
component and when you duble click it, you can edit its contents. But I
have changed to a more dynamic method of giving the user a blank slate and
letting them make the component from scratch. Then group it as a form of
'making' the component. Then double clicking will open a window that will
temporarily explode the component for editing.
So the grouping technique is a replacement of this one. But I learned a
lot about the arch with this one.
CL
> "CL [dnoyeB] Gilbert" <ThisisFake@Fakeness.xyz> wrote in message
> news:pan.2003.10.06.20.52.22.823555@Fakeness.xyz...
>> I have a component that contains other parts. I prevent its children from
>> being selected if I drag a box around this compomnent, or a box that just
>> contains its children by returning false to isSelectable if this
>> components parents parent is not a RootEditPart.
>>
>> Is this the architecturally correct way to do this? Is their a selection
>> policy or anything for the container? Anyway I can use a policy for this?
>>
>>
>>
>> Carl
|
|
|
Powered by
FUDForum. Page generated in 0.03281 seconds
] 
Search
Help
Register
Login
Home
