| Selecting a Node that has model children [message #192304] |
Wed, 17 August 2005 18:16  |
Eclipse User |
|
|
|
I have a stupid question about the EDiagram example: how do you make that
when I click anywhere in a node (not just the header) that the entire node
is selected? I have an application that does basically the same thing, but
when I click on the body of my node, which is represented by different
EditParts, the whole node is not selected. I looked through all the
EditPolicies in the EDiagram example and nothing struck me as being the
thing that make the difference.
|
|
|
|
|
| Re: Selecting a Node that has model children [message #192384 is a reply to message #192370] |
Thu, 18 August 2005 11:47  |
| Eclipse User |
|
|
|
Never mind, I figured it out...
"Felix L J Mayer" <felix.mayer@objectaid.com> wrote in message
news:de28g1$h76$1@news.eclipse.org...
> "Vineet Sinha" <vineet@csail.mit.edu> wrote in message
> news:de11i5$a2$1@news.eclipse.org...
>> Felix L J Mayer wrote:
>>> I have a stupid question about the EDiagram example: how do you make
>>> that when I click anywhere in a node (not just the header) that the
>>> entire node is selected? I have an application that does basically the
>>> same thing, but when I click on the body of my node, which is
>>> represented by different EditParts, the whole node is not selected. I
>>> looked through all the EditPolicies in the EDiagram example and nothing
>>> struck me as being the thing that make the difference.
>>
>> See AbstractEditPart.isSelectable (and methods that override it).
>
> I forgot to mention that I have already used that method like in the
> example ;)
> The strange thing is that my EditParts are basically the same as in the
> example:
> everyone of them uses the default implementation of
> AbstractEditPart.isSelectable(), only the CompartmentEditPart returns
> false.
>
|
|
|
Powered by
FUDForum. Page generated in 0.03310 seconds
Home