[Issue 6410] Can't delete text from arrow.

[email protected]
Newsgroups gmane.comp.lang.uml.argouml.issues
Message-ID <[email protected]>
http://argouml.tigris.org/issues/show_bug.cgi?id=6410



User mvw changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'mvw'
--------------------------------------------------------------------------------
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |INVALID
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Sat Jun  2 13:46:40 -0700 2012 -------
This issue has been reported many times before. The behaviour is intentional, as
I explained many times before, too - here again:

In short: 
the "notation" feature will allow to create and update modelelements, but not
delete any modelelement.

Longer:
ArgoUML allows the user to create (many) modelelements (at once) by entering
text on the diagram, in contrary to other tools. This ArgoUML feature is called
"notation".
E.g. entering something like this on a transition:
   trigger(a) [condition] / effect
creates 6 (yes!) modelelements connected to the transition. Please switch on the
"composite-centric explorer perspective" and see them for yourself.
The most common of these is the trigger, mostly a call event or signal event.

According the UML standard, it is the intention to use one trigger for several
transitions, not create a new one for every transition if they are triggered by
the same thing.

Suppose you have two transitions triggered by the same CallEvent "test". If you
now go edit the text "test()" on one of the transitions, and you delete the
text, what do you expect to happen? 
1. You could expect the trigger to be deleted, which would cause the trigger to
disappear from both transitions.
2. You could expect the trigger to be renamed to the empty string - which would
show the empty string on both transitions.
3. You could expect that the other transition remains unchanged, and that the
one edited alone is adapted in one of both ways described before.
4. Etc...

So, to circumvent the problem to make a correct choice, it is long ago decided
(by the developers of ArgoUML) that the "notation" feature will allow to create
and update modelelements, but not delete a modelelement.

The feature is consistently implemented throughout ArgoUML for all different cases.

This is a decision that I can stand behind, but I could accept another vision as
well. If someone would change this behaviour of ArgoUML, I would only accept
that if it is done consistently.

Hence, I put this issue on invalid.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=2968509

To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.