|
|
| Re: DragAndDrop- or Move-Command Issue [message #480695 is a reply to message #480680] |
Tue, 18 August 2009 09:04  |
 Timothy Marc
Messages: 547
Registered: July 2009 |
Senior Member |
|
|
Ed, well i see... this is a problem with the subset capapbilities of
UML2 genmodel. I've implemented an algorithm, that derives the
participants for a subset based on a given configuration of elements.
When moving the element in the tree, the already registered participants
are duplicated in the superset. But i changed it now into a more simpler
semantic.
/Timothy
Ed Merks schrieb:
> Timothy,
>
> Comments below.
>
> Timothy Marc wrote:
>> Hi all,
>>
>> just a single question: what is the operational semantic of a
>> Drag'n'Drop, respectively MoveCommand?
> If it's within a feature, I'd expect it to result in a move command.
> Otherwise I'd expect it typically to result in a remove and an add.
> You can look in DragAndDropCommand to see all the possible variations
> though, which are quite complex.
>> I've noticed, that a movement (simple reordering the elements in the
>> tree viewer manually) causes a new object creation? Is this correct?!
> I'd not typically expect that, but you'll see comments like this:
>
> // If there isn't an executable command we should maybe try a copy
> operation, but only if we're allowed and not doing a link.
> //
>> I was wondering why all features are unset by moving an element inside
>> the tree. And more precisely: is it possible to change this behavior
>> by overriding a command?
> I can't reproduce this behavior with any of my generated editors so it's
> hard to comment about the cause in your case...
>>
>> Thx
>> /Timothy
|
|
|
Powered by
FUDForum. Page generated in 0.02863 seconds
] 
Search
Help
Register
Login
Home
