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

rqt_plot: remove warning/debug message when backend not found #301

Merged
merged 1 commit into from
Feb 17, 2015

Conversation

trainman419
Copy link
Contributor

New users are confused by the log messages indicating that some of the rqt_plot backends are not found. These debug messages should be removed from the console log, and a message indicating that the backends aren't installed should be added to the backend selection dialog.

I've seen this 3 or 4 times in as many months on ROS answers; the most recent occurrence is: http://answers.ros.org/question/201721/rxplot-not-found/?answer=201784#post-id-201784

@Enfenion
Copy link

Enfenion commented Feb 9, 2015

I second this. Or the message should at least state that another backend was found and and is used.

@ablasdel
Copy link
Contributor

ablasdel commented Feb 9, 2015

I agree that warnings to the command line do not seem appropriate here as long as it finds something to use. The GUI for changing the backend already has instructions on what to install if you want to change them.

Would anyone be against removing these messages entirely?

At the very least changing them to "INFO" level instead of warning and adjusting the message to get the point across that everything is still AOK would be a great change.

@dirk-thomas
Copy link
Contributor

I don't think simply removing the messages is a good idea. Simply because then there is no indicator anywhere what happened.

Having some indication in the backend selection dialog sounds like the best approach to me. Does anyone want to provide a PR with that enhancement?

@ablasdel
Copy link
Contributor

The backend selection GUI already disables selection of the backends it can't find and points users to the installer of the backends in question.

This seems like enough to me.
What more do you think would be warranted?

@dirk-thomas
Copy link
Contributor

You are right, the settings dialog already provide a lot of feedback. I am just a bit concerned that it isn't very discoverable (which is a problem for all plugins).

What do you think - would the following be helpful?
Instead of the warning the plugin outputs an info message to the console stating which backend it has selected. Additional the message mentions that this can be changed in the plugins settings dialog.

@ablasdel
Copy link
Contributor

I think that makes sense but I would still downgrade it to an info level message not a warning since this will be displaying every time they launch unless they have all the backends installed.

@trainman419
Copy link
Contributor Author

As a GUI tool, I think all of the user's interaction should be through the GUI.

It sounds like the settings menu already covers the required behavior - it informs the user which back ends are available, and how to install them if they aren't found.

In that case, I think we should remove the command-line warning entirely.

I don't think the settings menu being discoverable is an issue here - once the user has discovered the option to change the back end, they're given all of the appropriate information for that context.

@dirk-thomas: if you think the settings menu is not discoverable enogh, that should be filed and handled as a separate bug.

@dirk-thomas
Copy link
Contributor

Sounds good. Go ahead and remove the console warnings then.

trainman419 added a commit to trainman419/rqt_common_plugins that referenced this pull request Feb 17, 2015
@trainman419
Copy link
Contributor Author

Implemented and converted to PR.

dirk-thomas added a commit that referenced this pull request Feb 17, 2015
rqt_plot: remove warning/debug message when backend not found
@dirk-thomas dirk-thomas merged commit b7ff4c5 into ros-visualization:groovy-devel Feb 17, 2015
@trainman419 trainman419 deleted the feature_301 branch June 8, 2015 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants