-
 

screen_grab package from screen_grab repo

screen_grab

Package Summary

Tags No category tags.
Version 0.0.2
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/lucasw/screen_grab.git
VCS Type git
VCS Version master
Last Updated 2024-11-17
Dev Status DEVELOPED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Publish a screen capture as an Image

Additional Links

Maintainers

  • Lucas Walter

Authors

No additional authors.

screen_grab

Capture the screen and publish it on a ROS sensor_msgs/Image topic

Currently this runs as a nodelet. screengrab.launch shows an example launch file, it will probably need to be copied and altered for integration in a real system.

roslaunch screen_grab screengrab.launch

A nodelet image display window will also pop up showing the captured image of the screen, and of course rqt_image_view or any image subscriber can be used.

The built package is available for jade:

sudo apt-get install ros-jade-screen-grab

But building for hydro and indigo ought to work.

A video of an earlier version: https://www.youtube.com/watch?v=Ys9BN4mJ_yc

Some discussion is here: https://plus.google.com/+LucasWalter/posts/f7fLhyWL3A4

CHANGELOG

Changelog for package screen_grab

0.0.2 (2016-01-26)

0.0.1 (2016-01-22)

  • Looks like opencv imshow can't be used from two nodelets in the same group.
  • Fixed nodelet xml for image show, now it works
  • Install launch files. It looks like image_view has some problems 'Could not create object of class type image_show::ImageShow as no factory exists for it.'
  • catkin_lint cleanup
  • New image_show was useful for debugging screen_grab nodelet, may move elsewhere later, also is much less cpu than image_view or rqt_image_view. ScreenGrab ndelet is now fully operational. #5
  • Looks like the setting/getting of parameters is working now (and maybe can be simplified further), but I haven't run image view as a nodelet yet. I have discovered that connecting to the nodelet manager with a bad node name brings it to a halt (am I not printing output to screen for it?), so maybe my image view command isn't right. If nodelets are that brittle then they become a lot less useful whatever the performance gains.
  • Nodelet merged with roi code, also dr is using private namespace.
  • Implemented nodelet #5, but need to merge with RegionOfInterest changes
  • #4 RegionOfInterest control in parallel to dynamic reconfigure.
  • Now dynamic reconfigure is working, though it would be nice to see if I can set slider maximums at start time and override the cfg.
  • Now can set the update rate dynamically, there is no Rate::set method but it can just be overwritten with new Rate instance.
  • Putting all parameters into a namespace, make sure everything uses relative namespace names
  • Have a launch file that also launch image_view
  • Using ros parameters to set x,y,width, & height, next add defaults to new launch file.
  • Taking code from vimjay screencap to work here, this does no conversion yet.
  • Contributors: Lucas Walter

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Dependant Packages

No known dependants.

Launch files

  • launch/screen_grab.launch
      • update_rate [default: 10]
      • use_rqt_image_view [default: true]
      • use_image_show [default: false]
      • use_image_view [default: false]

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged screen_grab at Robotics Stack Exchange