HCL RTist 11 2020.33 is now available with several improvements in various areas.

Organize Sources

The Organize Sources button is now available in the TC editor again. It can help you to set-up the Sources list of a TC in an optimal way so that the minimal number of model elements get transformed and built by the TC. The button opens a dialog which will analyze references in the model and suggest elements to add or remove from the Sources list.

organize sources

Context Sensitive Help for Properties

Context sensitive help is now available for the Properties view. Click the new Help button in the Properties view toolbar when you want to learn about the meaning of the many properties that can be edited in the Properties view.

Using CDATA in Model Files

When RTist model files are viewed outside of RTist they appear as XML documents where code and documentation texts can be difficult to read. This is because the escaping of certain characters that is mandated by XML – characters that are commonly used in C++ code (‘<‘, ‘>’, ‘”‘ etc). In this release we have introduced a new preference Modeling – Use CDATA when saving model files which can be set in order to store code and documentation text in XML CDATA sections. This means such texts can be stored as is, without any character escaping, which makes them much easier to read. Here is an example:

  • Without CDATA:


Without CDATA


  • With CDATA:




TC Editor Usability Improvements

It’s now much more pleasant to edit .tcjs files textually using the Code tab of the TC editor. We have implemented marking of occurrences when placing the caret on a name. All occurrences of that name are then highlighted in the editor. We have also implemented content assist, that saves you from a lot of typing. It is automatically invoked when you type certain characters (‘.’ and ‘=’) and you can also invoke it manually by pressing Ctrl + Space.

TC Editor Usability Improvements


Further steps were taken on our journey to fully support C++ 11. In this release we focused on the C++ 11 keyword ‘override’. The user interface now assists you to set-up this property correctly when redefining operations, and the model compiler uses ‘override’ for TargetRTS functions that are overridden in the generated code. Note that this change means that it’s now necessary to use a compiler that supports C++ 11 for compiling generated code. However, you can still generate code for older compilers by using a new preference RealTime Development – Build/Transformation – C++ – C++ code standard.

Learn more about HCL RTist or schedule a demo.

Comment wrap
Further Reading
Conjucating Certain Capsule Ports in HCL RTist
Secure DevOps | September 11, 2020
Conjugating Certain Capsule Ports in HCL RTist
Protocols in an RTist model are often binary, meaning that there are two connected ports typed by the protocol. The out-events for one of the ports are the in-events for the other port.
Developing Stateful, Event-driven and Real-time Applications
Secure DevOps | September 2, 2020
Developing Stateful, Event-driven and Real-time Applications
HCL RTist is an Eclipse-based modeling and development environment for creating complex, event-driven, real-time applications in C++.
Introducing Design Room ONE Version 2.1
Secure DevOps | July 23, 2020
Introducing Design Room ONE Version 2.1
The latest Sprint 2020.26 bring us a new version 2.1 of Design Room ONE available for HCL RTist users. In this new version authentication functionality has been significantly improved and lost its EXPERIMENTAL tag. One of the improvements includes refactoring the way the Design Room ONE server integrates with Keycloak for authentication. As a result, the configuration procedure is now easier: all the settings that need to be updated are now located in Design Room ONE’s main configuration file – server-config.json. Due to these improvements, there is now no need for Design Room ONE to store a Keycloak administrator key making this integration even safer, since Design Room ONE server would only be able to access pieces of Keycloak information it needs to manage access to its designs. You can refer to Authentication Setup for detailed instruction on migrating Keycloak realms configured with previous versions of Design Room ONE without loosing any information about users and their roles. Another update related to server configuration is the introduction of a single property dr_db_url controlling database connection — provides more flexibility and allows using password protected databases, which are standard in cloud environments like Azure or AWS. This is since version 2.1 Design Room ONE supports integration with Collaborative Lifecycle Management (CLM) tools version If you are using CLM tools to track your requirements with CLM (read System Requirements for the full list of supported versions and other requirements) you would be able to create “Derived From” links in your modeling tool e.g. HCL RTist from a model element to a requirement. These links will be visible in Design Room ONE after the model has been exported to the server. After that matching “Derives Architecture Element” links will be visible in your requirements management application and you would be able...
a/icon/common/search Created with Sketch.