rosconsole: ROS_DEBUG_THROTTLE_COND #2
Labels
enhancement
New feature or request
Milestone
Comments
|
Related to #68 |
dirk-thomas
pushed a commit
that referenced
this issue
Jan 26, 2019
* Enabled Windows Build * Add ROSCONSOLE_BACKEND_DECL for backend functions * Add ROSCONSOLE_LOG4CXX_DECL for log4cxx interface functions * Extract the impl interface to a separate header for impl dll to use (#2) * Add ROSCONSOLE_BACKEND_DECL for backend functions * Add ROSCONSOLE_LOG4CXX_DECL for log4cxx interface functions * Extract the impl interface to a separate header for impl dll to use * Fix bad merge (#3) * add comment about visibility macros (#5)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @ablasdel on January 8, 2013 22:42
A common use case for throttled rosconsole messages is to warn about some sanity-check condition being false, but not fill the screen with warnings. It would make sense to be able to say
ROS_DEBUG_THROTTLE_COND(5.0, !validityCheck(), "State is invalid!")
with the intended meaning that every 5 seconds, validityCheck is called, and if it's false the message is output. NAMED and STREAM variants would also be nice.
Copied from original issue: ros/ros_comm#69
The text was updated successfully, but these errors were encountered: