The development team has just finished working on sprint 2022.26, which resulted in a release of Model RealTime version 11.2 2022.26. Let's have a quick look at some of the highlights of this release.
Do not miss a unique chance to virtually meet other Model RealTime customers and the development team on September 28, 2022, by signing up for Model RealTime TechConnect here: https://hclsw.co/rtisttc2022. The event will have many interesting presentations including roadmap discussions.
Previously copying a name of a named element such as a Capsule, an Operation, or a Diagram was a bit cumbersome, but starting from sprint 2022.26 it can be done with a standard Copy command in Project Explorer view, which can be invoked with a toolbar button, top/context menu or a keyboard shortcut (Ctrl+C). Copied names can be pasted anywhere, no matter if you want them in the Code View or in a chat with your colleague. And yes, you can copy as many names as you like with a single command, they all will be pasted into separate lines.
Another improvement that makes the code cleaner is a new preference to automatically delete all whitespace at the end of the lines.
If this setting is enabled, then whenever you save the code snippet in the Code Editor or commit changes to the model in the Code View all trailing whitespace characters will be removed from all the lines.
Code to model synchronization dialog pops up every time Model RealTime detects that generated code has been updated and asks the user if they want to propagate the changes made to the generated code back to the model. One of the checkboxes available in that dialog, allows saving the model immediately after it was updated with the changes from the generated code. Now the state of this checkbox is controlled by a new preference in RealTime Development -> Code To Model Synchronization
This becomes handy when you want to control the state in which the dialog appears for the first time in a new workspace since the dialog will remember user's choices for future invocations.
External Projects Import view got a new feature. Now it will automatically create 2 workings sets when importing the projects. The projects a user has selected for import will get into the first working set named after the project that was selected first, and all their recursive dependent projects will be added to the second working set named like the first one plus "dependencies" suffix.
We have improved operation names' parser so it can handle tricky cases correctly. For example, if you want to define a cast operator, which would cast an object to an inner class or enum defined inside another class. In this case, the operation name should be operator OuterClass::InnerEnum such and other operations containing namespace separator (::) are now handled by Model RealTime correctly.
Have a great summer,
Alexander Strabykin
IBM Model RealTime Development Lead