Versions Compared

Old Version 10

changes.mady.by.user Developer

Saved on

compared with

New Version Current

changes.mady.by.user Developer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Expand
title[Expert Review Needed]Cache error occurred. How to handle it?

Close your modeling tool, delete all cache folders and start the program again.
Cache folders can be found in <user home directory>\.<modeling tool>\<version number>, for example <userhome>\.magicdraw\<18.2>.

If the problem still exists, please add the -Dcom.sun.media.imageio.disableCodecLib=true option into the JAVA_ARGS line in the modeling tool properties file, for example magicdraw.properties. A properties file is in <modeling tool installation directory>\bin.

See the example:

JAVA_ARGS=-Xmx4000M -XX\:PermSize\=60M -XX\:MaxPermSize\=200M -DLOCALCONFIG\=true -Dfile.encoding\=UTF-8 -splash\:data/splash.png -Dmd.class.path\=$java.class.path -Dcom.nomagic.osgi.config.dir\=configuration -Desi.system.config\=data/application.conf -Dlogback.configurationFile\=data/logback.xml -Xss1024K -Dcom.sun.media.imageio.disableCodecLib=true

 



Expand
title[Expert Review Needed]How do I turn on debug log mode?

To initialize log4j, open <MagicDraw installation directory>/data, and modify the debug.properties file.

Change the debug level for appropriate categories by specifying log4j.category.<category>=DEBUG or turn on debug for all categories log4j.rootCategory=DEBUG,SO.


Expand
title[Expert Review Needed]I have installed several versions of the modeling tool on Mac OS and the application can’t be opened using the .app file. How should I start a program?

Please restart your computer. After multiple updates or after installing different versions of a modeling tool on the same machine with Mac OS, sometimes it happens for unknown reason.


Expand
title[Expert Review Needed]I ran into a trouble when installing MagicDraw: Launching installer... Exception in thread "main" java.lang.NoClassDefFoundError: com/zerog/lax/LAX

In most cases such error appears when installer file is truncated or corrupted.

Please try to download an installer again.

Another option is that /usr/bin/java is an old version java. To check which java is used by installer, set environment variable LAX_DEBUG and launch installation again.

By default installer first uses java found in /usr/bin. But there is possibility to use specific VM when launching the installer. Please add parameter LAX_VM to launcher and second parameter path to java executable, here is an example (assuming that java is in /opt/j2sdk1.5.0_03):

./MD_UML_105_unix.sh LAX_VM /opt/j2sdk1.5.0_03/bin/java


Expand
title[Expert Review Needed]After the download the installer cannot be launched or it just appears on the screen and vanishes

Please check if the file is not truncated. You can see the exact file size at the download page.

...

Expand
titleMagicDraw 17.0.4 can be started neither on Mac OS X Lion nor on Mac OS X Mountain Lion. JRELoadError appears when trying to start the application. How can this be handled?

The error appears because the MagicDraw.app file cannot find the installed Java 6.

To handle the problem, please use one of the following workarounds:

  • Start MagicDraw using the mduml* file that can be found in <MagicDraw installation folder>/bin.
  • Install Java 6 in your computer and use the MagicDraw.app file to start MagicDraw 17.0.4.

This issue will be fixed in MagicDraw 17.0.5.

 


* If you are using MagicDraw 17.0.5 or later, the name of the property file is magicdraw.properties.

...

Expand
titleAfter installing MagicDraw on the Mac OS with Java (1.6.0_17), default Look & Feel does not function and the Mac menu bar is gone.

In order to fix the problem with the menu bar after java update on the Mac OS, you need to open /.magicdraw/16.6/data/global.opt and change the string "com.apple.laf.AquaLookAndFeel" to "apple.laf.AquaLookAndFeel".

Expand
titleWhen I saving project after I have upgraded Magicdraw to v16.6 I get a save error.

Save error appears saving project with modules when MagicDraw v16.6 is installed on top of MagicDraw v15.0 or earlier (using autoupdate functionality). This problem occurs because one or more old resource descriptors from MagicDraw v15.0 or earlier are corrupted.

To prevent MagicDraw project save error you need to install MagicDraw v16.6 to a new location – to a new and empty folder, for example, "MagicDraw 16.6". Note that on the first MagicDraw startut you can import MagicDraw environment options from previous MagicDraw installations.

You may download MagicDraw 16.6 from your personal or company profile on www.nomagic.com, also to obtain unlock keys.


Expand
titleWhen I run MagicDraw 18.5 on Mac OS X 10.11 El Capitan in the native full screen mode, why do most dialogs appear behind previously open dialogs?

This is a known issue with Mac OS X 10.11 El Capitan operating system. Most dialogs in the application will be displayed behind previously open dialogs, affecting usability of the user interface. There is no solution to this problem. Please try to downgrade the Mac OS to some earlier version.

...

Expand
titleThe file list dialog on Mac OS X doesn't respond appropriately when selecting folders

Fix for this problem is described at https://bugs.openjdk.java.net/browse/JDK-8006420

To solve the problem:

  1. Open the magicdraw.properties file, which is located in <MagicDraw* installation directory>/bin.
  2. From the JAVA_ARGS= line, remove the -splash\:data/splash.gif parameter

After this fix, on MagicDraw* startup, the spash screen will not be displayed for a few second, but the open file list dialog refresh problem will be solved.

The fix is sheduled into the nearest release.

 

Expand
titleWhy the Model Browser of my project doesn’t show newly created elements, and corrupted elements appear in it with no reason?

This happens because of the Model Browser refresh problem with MagicDraw 18.0.
To solve this problem, do one of the following:

  • Refresh the project (press F5).
  • Save the project (press Ctrl+S).
    • Change the Model Browser settings. For example, turn on the Show Auxiliary Resources option

    .