JointTrajectoryStreamer init() never called

[Google Code Exporter]

Running the JointTrajectoryStreamer class in the industrial_robot_client (e.g. 
using the motion_streaming_interface demo node) causes unexpected/uninitialized 
behavior.

When receiving a new trajectory command, the node prints a DEBUG message 
"Current state is: <garbage>".  At startup, the current state should be "0".  
When the JointTrajectoryStreamer's init() method isn't run, then the background 
thread isn't started to stream points to the robot, so the robot never executes 
the commanded trajectory.

The JointTrajectoryStreamer derived class provides an override implementation 
for one of the init() methods of the JointTrajectoryInterface base class.  A 
change to the base-class method signature was not echoed down to the 
JointTrajectoryInterface method, so now the "override" function doesn't 
actually work as an override and never gets called.

The method signature for the JointTrajectoryStreamer init method should be 
changed to match the base class.  This will allow the JTS's init() method to be 
called at the proper time.

I'm working on it now, and should have an update out shortly.

Original issue reported on code.google.com by [e-mail] on 14 Feb 2013 at 11:35

[Google Code Exporter]

Fixed in r1090 and r1091.  Updated JointTrajectoryStreamer's init() signature 
to match the JointTrajectoryInterface base class, so override behavior works 
properly.

Original comment by [e-mail] on 14 Feb 2013 at 11:57

• Changed state: Fixed