In the latest release 2.1.1 if your ROS2 message definition contains a wstring type, you get a "Bad field when parsing field" popup error. This PR includes wstring as a valid type for a message so that those topics can be subscribed to. In python wstring is treated the exact same as a normal string, and in c++ wstring is a u16string.
The latest base PlotJuggler 3.9.1 release also changes some import paths that make building from source fail, that import is fixed in this PR.
Testing Environment:
OS: Ubuntu 22.04
ROS2 Rolling as of 04/16/2024
PlotJuggler and ros_msg and plugin latest source as of 04/16/2024
FastDDS (rolling default)
In the latest release 2.1.1 if your ROS2 message definition contains a
wstringtype, you get a "Bad field when parsing field" popup error. This PR includes wstring as a valid type for a message so that those topics can be subscribed to. In python wstring is treated the exact same as a normal string, and in c++ wstring is au16string.The latest base PlotJuggler 3.9.1 release also changes some import paths that make building from source fail, that import is fixed in this PR.
Testing Environment: OS: Ubuntu 22.04 ROS2 Rolling as of 04/16/2024 PlotJuggler and ros_msg and plugin latest source as of 04/16/2024 FastDDS (rolling default)