Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix SteadyTimer check for backported ROS versions #71

Merged
merged 2 commits into from
Oct 10, 2018

Conversation

flixr
Copy link
Contributor

@flixr flixr commented Aug 30, 2018

SteadyTimer is also available on kinetic now, see https://github.com/ros/ros_comm/blob/kinetic-devel/clients/roscpp/CHANGELOG.rst

So also check for these backports...

@flixr
Copy link
Contributor Author

flixr commented Sep 20, 2018

friendly ping...

@jihoonl jihoonl merged commit 7a45912 into RobotWebTools:develop Oct 10, 2018
@flixr flixr deleted the steady_timer_check branch October 13, 2018 12:33
dirk-thomas added a commit that referenced this pull request Sep 19, 2019
* fix SteadyTimer check for backported ROS versions (#71)

i.e. on current kinetic

* Add PngStreamer (#74)

* lax rule for topic name (#77)

* Add a workaround for MultipartStream constant busy state (#83)

* Add a workaround for MultipartStream constant busy state
* Remove C++11 features

* Add "default_stream_type" parameter (#84)

This allows users to specify default stream type in their .launch files. Using a "ros_compressed" stream type sometimes
results in a much lower resource consumption, and having it set as a default is much nicer for end users.

* update changelog

* 0.2.0

* Fall back to mjpeg if ros_compressed is unavailable (#87)

* Update travis config (#89)

* Restream buffered frames with minimum publish rate (#88)

* Restream buffered frames with minimum publish rate

* Implement restreaming for ros_compressed_streamer

* update changelog

* 0.2.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants