Add methods to obtain the current config file from the robot #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using this commit:
You can actually do several interesting things with the
RobotConfigFile
andRobotConfigFileManager
objects (that's why I left them accessible). theRobotConfigFile
allows you to obtain an XML parser of the actual current configuration, as well as determine it's file path, so you can modify it and reload the config during robot operation (doing that during an OpMode would probably mess stuff up though). TheRobotConfigFileManager
is more of an implementation detail of the RC phone (hence why I left it accessible only from the activity) but can let you get finer control over how configurations are parsed and selected.