The following is a list of known problems and limitations in Visual Modeler 2.0. The number preceding each item is a bug tracking identifier. Please refer to this number if you have a support question about the problem.
Create a logical package cat, then open cat's principal diagram and
place another view of cat there. Copying cat causes it to get the
"no model item" adornment.
If an icon name spans multiple lines (that is, contains a carriage return) only the last line of the name is visible in the icon's specification.
Workaround: Use the text box on the icon to view the entire name. Better yet, avoid using carriage returns or spaces in icon names.
For example, update cannot resolve unnamed model items.
Workaround: Be sure to name all items in the model. (Naming relationships is not required.)
Assume that you have classes in your model that have method arguments of class X. If you go into class X and change its name to Y, the arguments are not updated; they remain of class X, not class Y.
For example, Change Into is not grayed out on the Edit menu even when all the items on the Change Into submenu are grayed out.
Workaround: Can usually be fixed up by dragging the substate out and then back in.
If Show Method Signature is set to ON for a given model,
but set to OFF in the current Visual Modeler session, the operation will
not be shown when the model is read in.
Workaround: The setting for Show Method Signature
should be chosen ONCE for all users who are sharing models
and NOT be changed.
To select or raise the property sheet for an generalization relationship, place your cursor on the relationship line rather than the arrow head.
You can redisplay the windows by pressing F2 or by minimizing and maximizing Visual Modeler.
Visual Modeler crashes sporadically when some utility programs are running in the background. After Dark is such a utility; the mouse-utility Point32 is another.
If the Cancel button in the Cancel Printing dialog box does not work (after you do a Print Specifications or Print Diagrams), press the escape key to force a cancel. The reason the Cancel button does not work is usually because of insufficient disk space or not enough free memory.
To see the entire diagram in another application, choose View > Fit in Window in Visual Modeler before you copy and paste into the other application.
If you encounter this problem, restart PowerPoint and copy/paste again with "visibility as icons" off.
Because the Setup wizard does not completely register Visual Modeler with Windows, if you attempt to start Visual Modeler the first time by double clicking a model in Windows Explorer, Visual Modeler may crash. After Visual Modeler has been run once, the registration is complete and double clicking model files will work correctly.
If a class icon is incorrectly resized after a method or a property is added, you can select the class and use the mouse to resize it.
Visual Modeler does not support label buttons, but there may still be references to label buttons in pictures of screens in the documentation.
There are several problems with "What's This?" in the online help:
No Help Topic is associated with this item.
This does not necessarily imply that there is no help available for the item. Often the "What's This?" help mechanism for the item simply has not been connected. Click on the Help button in the dialog box and you will be able to traverse to the information you need.
In short, when you are in a Visual Modeler dialog box and "What's This?" help (or the ? in the window banner) does not help you, try the Help button instead.
UML packages are intended to be unique name spaces. However, Visual Modeler does not support separate name spaces; names must be unique throughout the entire model. So, for example, in models:
The Visual Modeler Add-Ins can operate only if a single Visual Basic 5 application is running. If multiple Visual Basic 5 applications are running, the code generation and reverse engineering tools in Visual Modeler cannot be used.
No code is generated for model items in the Component view, that is, for EXEs and DLLs.
When exporting a model to the repository, the documentation is not saved.
The Creatable code generation option for classes does not use the correct Visual Basic 5 naming. The Creatable option values in Visual Modeler correspond to the following instancing properties in Visual Basic 5: OnNewProcess = 3-SingleUse, GlobalOnNewProcess = 4-GlobalSingleUse, InSameProcess = 5-MultiUse, GlobalInSameProcess = 6-GlobalMultiUse.
The Visual Modeler Add-In Menus may, under some circumstances, cause Visual Basic 5 to crash when quitting the application. This problem occurs if the Visual Modeler Add-In Menus is running in the add-in manager together with either "VB Add-In Toolbar" or "Source Code Control". Please refer to the Microsoft Knowledge Base, article ID Q167213, for explanation and workarounds.
In some configurations the installation program may have problems
registering the DLLs used by Visual Modeler. If, for example, the Tools>
Class Wizard command fails to execute, run the REGRVB.BAT program from the
folder in which Visual Modeler is installed.
The order system example, located in the \Samples\Ordersystem folder, needs
the Microsoft DAO 3.5 object library. Your Visual Basic 5 product may be
installed without this component. If the DAO library is missing, you can add
it in the following way:
Visual Modeler supports only one name space; a class name must be unique within a
model. In OLE, an ActiveX component constitutes its own name space. Thus, two ActiveX
components can export the same interface name. You can instruct the
Visual Modeler reverse engineering tool to create unique class names by
combining the ActiveX name and the class name, for example: DAO.Database.
The default behavior of Visual Modeler is to use short ActiveX names. To
use long ActiveX names, change LongActiveXNames to Yes in your rose.ini
file, which is found in the Windows folder.
Visual Modeler synchronizes your Visual Basic project and model
during code generation and reverse engineering by removing deleted members.
The default behavior in Visual Modeler is to remove members by commenting
the code. To turn this off and have the tool completely remove the members from
the code, set CommentMethods to No in your rose.ini file, which is found in
the Windows folder.
User-defined collection classes can be automatically created in Visual Modeler by changing the CollectionClass option for a class. To delete a created collection class from the model:
If you choose to build a Find database of a subset of the available help files using the "Customize search capabilities" alternative, you may get the error message "Unable to display the Find tab", or the resulting database may contain words from help files other than the selected files.