Solutions

When running some of the RTI tools on Linux (e.g. RTI Shapes Demo, RTI Launcher) you may see the following or similar warning messages thrown by GTK/GDK: (Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed) or Gdk-WARNING **: gdk_window_set_icon_list: icons too ...
1965 reads — 0 comments
When localization variables (LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_MONETARY, LC_NUMERIC, LC_TIME) are set to non-US values, a user could get an error similar to the following: "Your license has expired (Expiration Date: 01/01/1970)." A workaround to avoid this error is to change the ...
1195 reads — 0 comments
If you are running into problems compiling the shipped examples or the generated Hello World example from rtiddsgen on a non-Windows platform, one of the first things to check is if your installation directory resides in a path that contains spaces. If it does, then the solution will be to redefine ...
3777 reads — 0 comments
Description The discovery phase in DDS applications can be considered a high throughput scenario under some circumstances. Some examples are: The applications have a lot of DDS entities. More than 2 hosts are involved. The type definitions are sent within the discovery packets (i.e., TypeCode and ...
3710 reads — 0 comments
The following examples demonstrate how to use the Modern C++ API: Lambda Content Filter (C++11) Content Filtered Topic (C++03) Asynchronous Publisher (C++03) Batching and Turbo Mode (C++03) Builtin Topics (C++03) Listeners (C++03) Polling QueryCondition (C++03) Ordered Presentation (C++11) ...
5831 reads — 0 comments
In a scenario where multiple DataWriters come up and go away in the system, a matching DataReader application will experience a continual memory growth, this may be confused with a memory leak. This observed behavior is due to the fact that DataReader entities must maintain information about the ...
2224 reads — 0 comments
Note: Applies to RTI Connext 5.2.0 and above. The following error: PRESParticipant_checkTransportInfoMatching:Warning: discovered remote participant 'yyyyy' using the 'shmem' transport with class ID 2. This class ID does not match the class ID 16777216 of the same transport in the local participant ...
6459 reads — 6 comments

Pages