ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
If you look at the api for ros::waitForShutdown() it says that it will cause the current program to wait for a ctrl-c.
You definitely don't want to run that from a qt callback or it will lock up your program.
Try taking out the ros::waitForShutdown() and tell me what kind of behavior you get.
2 | added link to spinning on the wiki |
If you look at the api for ros::waitForShutdown() it says that it will cause the current program to wait for a ctrl-c.
You definitely don't want to run that from a qt callback or it will lock up your program.
Here is some info on the behavior: http://www.ros.org/wiki/roscpp/Overview/Callbacks%20and%20Spinning
Try taking out the ros::waitForShutdown() and tell me what kind of behavior you get.
3 | No.3 Revision |
If you look at the api for ros::waitForShutdown() it says that it will cause the current program to wait for a ctrl-c.
You definitely don't want to run that from a qt callback or it will lock up your program.
Here is some info on the behavior: http://www.ros.org/wiki/roscpp/Overview/Callbacks%20and%20Spinning
Try taking out the ros::waitForShutdown() and tell me what kind of behavior you get.
4 | Added a link to the api referenced |
If you look at the api for ros::waitForShutdown() it says that it will cause the current program to wait for a ctrl-c.ctrl-c.(http://mediabox.grasp.upenn.edu/roswiki/doc/api/roscpp/html/namespaceros.html#af068034d937093fdb0d5aaa1e0d9e249)
You definitely don't want to run that from a qt callback or it will lock up your program.
Here is some info on the behavior: http://www.ros.org/wiki/roscpp/Overview/Callbacks%20and%20Spinning
Try taking out the ros::waitForShutdown() and tell me what kind of behavior you get.