The patch as it currently stands will not publish the default position messages unless using the GUI or a source list. As that was my original use case for the node, I think it'd make sense to add parameters for whether to publish positions velocities and efforts by default, with positions by default True. Would that fit with your usage? On Sat, Jul 7, 2012 at 9:58 PM, David Lu!! wrote: > That's probably me. I'll take a look. > > On Sat, Jul 7, 2012 at 9:57 PM, David Lu!! wrote: >> That's probably me. I'll take a look. >> >> On Fri, Jul 6, 2012 at 9:52 PM, Michael Ferguson wrote: >>> I would also suggest emailing the maintainer of the package/stack, with a >>> link to the ticket, as not all repositories are set up to automatically >>> email the maintainer when a new ticket is filed. >>> >>> -Fergs >>> >>> >>> On Fri, Jul 6, 2012 at 7:50 PM, Jack O'Quin wrote: >>>> >>>> On Fri, Jul 6, 2012 at 9:35 PM, Jim Rothrock >>>> wrote: >>>> > I have cloned https://kforge.ros.org/robotmodel/visualization and >>>> > modified >>>> > joint_state_publisher so that it supports the velocity and effort >>>> > components >>>> > of the joint states. If the joint states published on topics in >>>> > source_list >>>> > contain velocities or efforts, my version of joint_state_publisher >>>> > publishes >>>> > those values along with the joint positions. How do I submit a patch to >>>> > joint_state_publisher? Do I need to become a member of the Robot Model >>>> > group >>>> > on kforge.ros.org, then push the change to the repository? >>>> >>>> For most components it works well to open a Trac enhancement ticket >>>> with your patch attached. >>>> -- >>>> joq >>>> _______________________________________________ >>>> 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 >>>