VisualAge(R) for Java(TM)

Version 3.5

Visual Composition Editor

RELEASE NOTES

Table of contents

1.0 Limitations and known problems
      1.1 Morphing
      1.2 Constructing visuals from source with array properties 
      1.3 Class path information lost when exporting a bean to a directory or a JAR
      1.4 JAR/Zip files added to the workspace class path are not applied immediately    
2.0 Hints and Tips
       2.1 Delete main() on copied/moved/renamed classes
       2.2 Using and manipulating JApplets       

1.0 Limitations and known problems

1.1 Morphing beans

When morphing beans, the order of  connections from the bean may not be maintained. Select Reorder Connections From from the pop-up menu of the morphed bean, and reorder them.

1.2 Constructing visuals from source with array properties

When reconstructing the visuals of beans that possess array type properties, be sure that the leaf type has a registered property editor. Otherwise, VisualAge for Java will not be able to generate the correct initialization code for that property. You will have to enter your own codestreams into the array editor.

1.3 Class path information lost when exporting a bean to a directory or a JAR file

If you export a bean to a directory or a JAR file and then import it, the class path information stored with the bean is lost. When you run the imported bean, you may receive a NoClassDefFound exception. Before running the class, set the classpath.

1.4 JAR/Zip files added to the workspace class path are not applied immediately

When you add JAR or zip files to the Workspace class path via the Window > Options... dialog, they do not get applied immediately. Add or delete any project or package or restart the IDE for the changes to take effect.

2.0 Hints and Tips

2.1 Delete main() on copied/moved/renamed Classes

If you have copied, moved, or renamed a visually composed class, delete main() and save the class. By deleting main(), you remove  obsolete code that otherwise is not overwritten. Once the obsolete main() has been deleted, VisualAge recreates a valid main() when you save the class.

2.2 Using and manipulating JApplets

To add a JMenuBar to a JApplet you must first Drag its contentPane to the freeform. This will allow you to Drop the JMenuBar onto the  JApplet and not the JPanel that is the contentPane.

If you have subclassed a JApplet and want to change its size or position on the Visual Composition page, you must make sure that you select and manipulate the JApplet, not its contentPane. Since the JApplet's contentPane completely covers the JApplet, you should select the JApplet using the Beans List and then manipulate the selection handles and border.

This technique of using the Beans List is useful in many situations where one or more children of a container completely covers the container.