-
Notifications
You must be signed in to change notification settings - Fork 914
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
Allow empty machine attribute #274
Comments
Wouldn't it be sufficient if you use |
It would, but it require to have defined localhost as a machine in every such launchfile. |
I still think that allow machine to be empty would be the better solution. This is what you are suggesting?
|
None of the attributes in roslaunch currently supports this kind of behavior. In order to stay consistent that rule would need to apply to all attributes (e.g. This would require some effort to investigate the effect on all attributes and describing the consequences of such a change. Since the maintainers do not have the time to address this in the near future the issue will be marked with the milestone untargeted. Any contribution on this is highly welcome. |
enable display of depth image thumbnails in rqt_bag
@dirk-thomas @liborw I've got the same issue. |
In the meantime some attributes started to allow empty values (e.g. the include tag #882). So allowing an empty machine tag doesn't sound that different anymore. A generic approach (optional attributes with an empty value are considered equal to the attribute not being specified) would be preferred. But any pull request would be appreciated. Also if it only implements the handling of an empty machine tag. |
Solution proposed in #1885. |
* Allow empty machine tag. Fixes #274. * Fix tests for machine arg in node tag. * Remove obsolete test. * Remove obsolete test
Allowing empty machine attribute of node tag would help to make a launch-files with optional machine argument.
An example:
The text was updated successfully, but these errors were encountered: