Investigate and fix timing issues when getting transforms from displays

[jacobperron]

Follow up #483.

It's possible that a similar issue to #483 may occur with other displays; rendering will fail if the fixed frame is not static. This may occur if calls to the frame managers getTransform() or transform() functions fail when provided a non-zero timestamp.

Here is a list of displays that request transforms, which we should confirm render properly when in a moving frame:

• Axes
• Camera
• GridCell
• InteractiveMarkers
• Marker (marker_base.cpp)
• Odometry
• Path
• Polygon
• PointCloud (point_cloud_common.cpp)
• PointStamped
• Pose
• PoseArray
• PoseCovariance
• Range
• Wrench

[olmerg]

There exist some prevision to solve this issue?

[jacobperron]

There exist some prevision to solve this issue?

I don't have bandwidth in the near-term to look at this issue. Any help is appreciated.