Repository navigation
Import taskdata xml - #41
Merged
Merged
Conversation
…ange-check imported values
… it, trim comments, and keep the open pool when a .ddop fails to load
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe your changes
This adds File -> Import ISOXML. It reads the device description out of an ISOXML TASKDATA.XML and loads it as a DDOP, so a device exported from an FMIS or by our own Export as ISOXML can be edited again.
examples/, next to a new exampleTASKDATA.XML.How has this been tested?
New
task_data_import_testimportsexamples/TASKDATA.XML, checks every device and object against the file, and checks the result survives an export and re-import. It also checks that broken files are rejected.cmake -S . -B build -DCAN_DRIVER=None -DSDL_CCACHE=OFF cmake --build build ctest --test-dir build --output-on-failure