Sure, https://code.ros.org/trac/ros/ticket/3174. I wasn't sure what
component to use--I didn't see ros_comm as an option--so I left it
unspecified.

Cheers,
Pat

On Fri, Dec 3, 2010 at 11:40 PM, Ken Conley <kwc@willowgarage.com> wrote:
> You bring up a good point -- can you file a ticket? It's mainly an
> implementation artifact right now, though easy enough to fix.  I may
> have time before we freeze ros_comm for 1.4.
>
>  - Ken
>
> On Fri, Dec 3, 2010 at 10:31 PM, Patrick Bouffard
> <bouffard@eecs.berkeley.edu> wrote:
>> I'm not sure if this a bug or a 'feature', but I'm seeing that if I do
>> something like:
>>
>> rostopic pub -r 50 /sometopic geometry_msgs/TransformStamped '{header:
>> auto, child_frame_id: /bla, transform: {translation: {x: 0, y: 0, z:
>> 0}, rotation: {x: 0, y: 0, z: 0, w: 1}}}'
>>
>> or
>>
>> rostopic pub -r 50 /sometopic geometry_msgs/TransformStamped '{header:
>> {stamp: now, frame_id: foo}, child_frame_id: /bla, transform:
>> {translation: {x: 0, y: 0, z: 0}, rotation: {x: 0, y: 0, z: 0, w:
>> 1}}}'
>>
>> .. then the header timestamp is populated, but only with a single time
>> (I guess the time the first message is sent). It would make more sense
>> to me to have the timestamp change with every message. Is there a
>> reason it doesn't?
>>
>> Thanks,
>> Pat
>> _______________________________________________
>> ros-users mailing list
>> ros-users@code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-users
>>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>