This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 56

Summary:	Refuse to delete last nail of self-loop
Product:	UPPAAL	Reporter:	Ulrik Nyman <ulrik>
Component:	GUI	Assignee:	Gerd Behrmann <behrmann>
Status:	RESOLVED FIXED
Severity:	enhancement
Priority:	P1
Version:	3.5.7
Hardware:	All
OS:	All
Architecture:

Description Ulrik Nyman 2003-09-10 21:12:40 CEST

The fact that the delete option for a nail and a transition shares the same name
in the popup menues can cause the user to mistakenly think that he/she has
deleted a transition when actually he/she has only deleted a nail in the
transition. This can occur when two transitions go from state A to state B and
the one (C) is direct and the other (D) has exactly one nail. If the D
transition has no Guard, Sync. or Update (yet) and the nail is deleted this
transition (D) will seem to disappear, but actually it will just coincide with
the C transition.

Comment 1 Ulrik Nyman 2003-09-10 21:15:16 CEST

Parhaps the names in the popup functions should be "delete transition" and
"delete nail".

Comment 2 Gerd Behrmann 2003-09-11 09:11:24 CEST

In fact, I think UPPAAL should refuse to delete the last nail. If I remember
correctly, you cannot create such invisible transition in the first place, so
you should not be able to "downgrade" a loop with one nail to a loop without any
nails.

Comment 3 Gerd Behrmann 2003-09-11 19:14:27 CEST

Changed the label on the delete menu item. I leave this bug open, since I feel
there is a bigger issue with having multible transitions between the same two
locations (as descriped by the reporter), but there is no time to fix this for 3.4.

Comment 4 Gerd Behrmann 2005-06-29 21:17:05 CEST

Moved enhancement request to 3.5.7, as only bug fixes are allowed in previous releases.

Comment 5 Gerd Behrmann 2006-03-10 15:36:55 CET

I changed it such that deleting the last nail of a self loop also deletes the edge.