Good point - I hadn't run into a usage scenario where I needed it so
was curious about that.
Adding a timeout/abort to the client.waitForExistence() call in
NodeletInterface::unloadNodelet is a better option?
Regards,
Daniel.
On 10 November 2010 08:32, Josh Faust <jfaust@willowgarage.com> wrote:
>>
>> You'll notice I commented out the
>>
>> //ni.unloadNodelet (name, manager);
>
> This is actually not correct. There are times when you want to keep the
> manager up but kill a different launch file that loaded nodelets into that
> manager. This prevents them from unloading.
> Really the unloadNodelet call needs a timeout.
> Josh
> _______________________________________________--
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
Phone : +82-10-5400-3296 (010-5400-3296)
Home: http://snorriheim.dnsdojo.com/
Yujin Robot: http://www.yujinrobot.com/
Embedded Ros : http://www.ros.org/wiki/eros
Embedded Control Libraries: http://snorriheim.dnsdojo.com/redmine/wiki/ecl
_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users