Author: bobtarling Date: 2010-01-30 10:01:34-0800 New Revision: 17941 Modified: trunk/src/argouml-app/src/org/argouml/uml/diagram/state/ui/FigState.java
Log: Removed comments suggesting Figs inheritance should mirror UML. Inheritance may not always be the way as it could ties us to a specific UML version. Modified: trunk/src/argouml-app/src/org/argouml/uml/diagram/state/ui/FigState.java Url: http://argouml.tigris.org/source/browse/argouml/trunk/src/argouml-app/src/org/argouml/uml/diagram/state/ui/FigState.java?view=diff&pathrev=17941&r1=17940&r2=17941 ============================================================================== --- trunk/src/argouml-app/src/org/argouml/uml/diagram/state/ui/FigState.java (original) +++ trunk/src/argouml-app/src/org/argouml/uml/diagram/state/ui/FigState.java 2010-01-30 10:01:34-0800 @@ -57,12 +57,8 @@ import org.tigris.gef.presentation.FigText; /** - * The fig hierarchy should comply as much as possible to the hierarchy of the - * UML metamodel. Reason for this is to make sure that events from the model are - * not missed by the figs. The hierarchy of the states was not compliant to - * this. This resulted in a number of issues (issue 1430 for example). Therefore - * introduced an abstract FigState and made FigCompositeState and FigSimpleState - * subclasses of this state. + * Abstract class with common functionality for all Figs representing a UML + * State element. * * @author [email protected] * @since Dec 30, 2002 ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=5905&dsMessageId=2443368 To unsubscribe from this discussion, e-mail: [[email protected]].
