Passing all command-line arguments to Property Object

[David-Estevez]

When extracting a group from a Resource Finder, only arguments coming from the config file are passed to the Property Object. Command-line arguments are ignored, and this may cause problems in the future.

Possible solutions:

• Append command line arguments to group arguments coming from the file as a new group in the Property Object
• Add support in YARP for extracting parameters depending on the origin of them (either command-line or file)

[PeterBowman]

For instance, let's take oneCanBusOneWrapper.ini. The name property to the [wrapper0] group is set to /wrapper0 in the .ini file. I'd expect that the following command would override the default value and pick /myPort instead (given also a default context and .ini config file, therefore no --context nor --from are shown here):

$ oneCanBusOneWrapper --wrapper0::name /myPort

The custom port is correctly parsed by yarp::dev::ResourceFinder, but dismissed during the initialization by yarp::os::Property::fromString().

Edit: tested on YARP 2.3.70.2.

[PeterBowman]

Relevant lines upstream: ResourceFinder.cpp. I'd deem that placing the call to yarp::os::Property::fromConfigFile() last would give precedence to command-line user arguments over --from.

[PeterBowman]

Add support in YARP for extracting parameters depending on the origin of them (either command-line or file)

Compare:

• yarp::os::Property::fromArguments
• yarp::os::Property::fromConfigFile

...and others.

[PeterBowman]

Looks like the ResourceFinder mechanism works as intended, i.e. it correctly merges both command-line and config file properties and gives more precedence to the former (via find). However, we need to use Property::fromString here which, in turn, picks the latter. Compare docs for fromConfigFile and fromString.

[PeterBowman]

Reported upstream at robotology/yarp#1889.

[PeterBowman]

Reported upstream at robotology/yarp#1889.

The former launchManipulation app has been improved and renamed to launchCanBus in #20. Also, the .ini parse system has been fully revamped (#237) and there is currently no urgent need to accept additional command line arguments in our CAN-based tools. Therefore, I'm marking this as invalid and superseded by the upstream issue.

[PeterBowman]

Add support in YARP for extracting parameters depending on the origin of them (either command-line or file)

See yarp::os::ResourceFinderOptions and related methods at yarp::os::ResourceFinder.