When you save a communication diagram as an SVG image, the fill colors for lifelines might not save correctly. To work around this issue, save the communication diagram as a GIF or JPEG image.
When you work with an editable diagram, the copy shortcut key (Ctrl+C) and paste shortcut key (Ctrl+V) might not work in text fields. To work around this issue, copy and paste text by using the Edit menu:
- Select the text to copy.
- Right-click the selection; then click Copy.
- Create a new text diagram element.
- Right-click the text diagram element; then click Paste.
When you work with a UML diagram, you cannot display constraints on association endpoints.
When you work with state machine diagrams, you can change the visibility of a state element. However, in the State view, the decorator of the state element might not update to reflect the visibility change.
If you display a lifeline that represents a property of a specific kind of classifier or a stereotyped element, the decorator icon is not displayed. Changing the stereotype and visibility settings has no effect. To work around this issue, you can differentiate the lifeline by changing its color.
When you generate Javadoc documentation for a UML diagram from a generated Ant script, the script runs to completion, but throws an exception. You can ignore the exception.
You cannot create a new operation on a C++ sequence diagram. To work around this issue, update the C++ source code to include the new operation.
When you double-click a constraint violation in the Problems view, the element opens in the UML Model Editor. However, the element should open in the diagram editor.
In the Diagram Navigator, the architectural discovery pattern count indicates the number of matches found at the time of analysis. If you update the workspace by importing new projects, or by closing existing projects, the count does not update. To update the count, run the analysis again.
When you invoke a command that displays a UML diagram, such as a file with an .emx, .epx, .dnx, or .tpx file extension, in text mode, the text editor might not display the file properly. To work around this issue, complete the following steps:
- In the Model Explorer view, select the diagram files
- Right-click the selection, then click Properties.
- Click the Info tab.
- Under Text file encode, click Other.
- Select UTF-8 from the drop-down list.
- Click Apply.
- Click OK.
When importing an Enterprise JavaBeansTM (EJB) diagram from WebSphere Application Developer, Version 5.1.1, relationship connectors may not appear properly. To work around this issue, select the connector(s) and in the Properties view, under Appearance, clear the Avoid obstructions check box.
When working with a UML diagram, the Show Related Elements operation can return a large number of elements, which may cause your computer to run out of memory. This issue is most common when you specify a search level greater than one, and when you search for all relationships. To work around this issue, specify a lower search level value, and rerun the query. This information also applies to Browse diagram queries.
Return to the main readme file