You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! This is more of a general question than an issue. Is there a specific reasoning as to why the ROS message types are structs managed by TSharedPtrs instead of UObjects or UStructs? Being unable to utilize the messages directly in Blueprints seems like a huge restriction.
The text was updated successfully, but these errors were encountered:
Hi @Sage-of-Mirrors
This is mostly due to the architecture of the project. The pure communication via rosbridge was developed and tested with a separate library (https://github.com/Sanic/rosbridge2cpp). This is why the data structures don't know anything about UE4, because it was meant to be usable in different contexts as well.
Hello! This is more of a general question than an issue. Is there a specific reasoning as to why the ROS message types are structs managed by
TSharedPtr
s instead ofUObjects
orUStructs
? Being unable to utilize the messages directly in Blueprints seems like a huge restriction.The text was updated successfully, but these errors were encountered: