svn commit: r17073 - trunk/src/argouml-app/src/org/argouml/notation/providers/uml/StateBodyNotationUml.java

Michiel van der Wulp <[email protected]>
Newsgroups gmane.comp.lang.uml.argouml.cvs
Message-ID <[email protected]>
Author: mvw
Date: 2009-04-08 06:20:43-0700
New Revision: 17073

Modified:
   trunk/src/argouml-app/src/org/argouml/notation/providers/uml/StateBodyNotationUml.java

Log:
Reuse settings.

Modified: trunk/src/argouml-app/src/org/argouml/notation/providers/uml/StateBodyNotationUml.java
Url: http://argouml.tigris.org/source/browse/argouml/trunk/src/argouml-app/src/org/argouml/notation/providers/uml/StateBodyNotationUml.java?view=diff&pathrev=17073&r1=17072&r2=17073
==============================================================================
--- trunk/src/argouml-app/src/org/argouml/notation/providers/uml/StateBodyNotationUml.java	(original)
+++ trunk/src/argouml-app/src/org/argouml/notation/providers/uml/StateBodyNotationUml.java	2009-04-08 06:20:43-0700
@@ -83,13 +83,9 @@
         return "parsing.help.fig-statebody";
     }
 
-
     @Override
     public String toString(Object modelElement, NotationSettings settings) {
-        return toString(modelElement);
-    }
 
-    private String toString(Object modelElement) {
         StringBuffer s = new StringBuffer();
 
         Object entryAction = Model.getFacade().getEntry(modelElement);
@@ -125,7 +121,7 @@
                 }
                 /* TODO: Is this a good way of handling nested notation? */
                 s.append((new TransitionNotationUml(trans)).toString(trans,
-                        NotationSettings.getDefaultSettings()));
+                        settings));
             }
         }
         return s.toString();

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

To unsubscribe from this discussion, e-mail: [[email protected]].
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.