This is a list of known issues for Dezyne:
- In order to avoid error dialog windows and strange looking System Views we advise that you store files belonging to only one modelling project and only one version of them in an Eclipse Project, sometimes referred as a Modelling Project
- In the Eclipse based stand-alone client the Views (i.e. system views, state charts, state and event tables, and sequence charts) are not displayed if the Dezyne model file is not included in an Eclipse Project, sometimes referred as a Modelling Project
- Views (i.e. system views, state charts, state and event tables) are not cleared if they can not be updated due to an error in the model or due to missing data
- The Export to image feature is not working in Dezyne Release 2.x.y
- The Print feature is not working in Dezyne Release 2.x.y
- In addition to the Eclipse proxy settings, also the ‘http_proxy’ environment variable has to be set. See ‘dzn –help’ for instructions.
- The blocking keyword has meaning for C++ code generation only.
- In case the daemon is stopped, it will be restarted automatically. In Eclipse however one has to do a logout;login to reconnect to the new daemon process.
- The absence of an open source header in the generated code does not imply commercial support.
- Long list of guards lead to nested if-then-else constructs in the generated code which might cause a ‘nesting overflow’ error in VisualStudio during compilation.
- It seems that the Dezyne Infocenter is not accessible from within Eclipse if Dezyne is installed as a plugin
- The webclient has been removed, evaluation from the browser is supported via the command line.
- Users having an old version of Node.js installed on their system might experience problems with starting a simulation. We recommend that our users install the latest (stable) version of Node.js or use the one installed by the Eclipse based stand-alone Dezyne client.
- In case that views, i.e. system diagrams, state charts, state and event tables, or sequence views, are not visible under Linux, please install libwebkitgtk-1.0.
- Those who download and use the Eclipse based stand-alone client without Java RTE need to ensure that they have Java 8.0 installed on their system.
- In case your Native/Default browser is IE10 or older please switch your browser in Dezyne to the ‘Built-in’ browser. Switch from ‘Native Browser’ to ‘Built-in Browser’ in the dialog window after selecting Window->Preferences->Dezyne->Browser. Don’t forget to restart Dezyne after clicking on Apply.
- Due to some limitations/problems with Eclipse and GTK 3 there are some issues when installing Dezyne as a plugin, therefore GTK 2 is needed. Please add the following two lines before ‘-vm’ in your Eclipse.ini:
- When using Dezyne service 2.1.0 there can be cases when the Simulator reports wrongly a deadlock which is correctly not reported by the Verifier. Please make sure that you use service 2.1.1 to avoid this situation.
- The Dezyne 2.1.0 Eclipse based stand-alone client is not able to install the Dezyne command line client, a.k.a. dzn, on MacOSx. Please download and install the Dezyne 2.1.1 Eclipse based stand-alone client.
- Due to access rights to files the Dezyne 2.0.0 Eclipse based stand-alone client with Java RTE can not be updated to 2.1.0. Therefore, if you want to use the Eclipse based stand-alone client you have to download it and pack it out. “Old” workspaces can be still opened in the new client.
- The Dezyne 2.x.y Eclipse based stand-alone client does not work with the Dezyne command line client, a.k.a. dzn, 1.3.0. Please uninstall this version. The Dezyne Eclipse based stand-alone client will install the new Dezyne command line client automatically.
Please let us know if you find more issues so that we can keep our users informed and we can address them as soon as possible.