...
Old xml files defining cases could be imported with this tool.
Multiple files could be selected. Importing twice a file is not a problem, the case will be created once, because a unique id is assigned to each case.
Button to define a new case:
Then the window to define all possible options must be filled.
Information is classified in basic and advanced tabs.
name: It is the name that appear in the first column of each case. Really is not compulsory and could not be unique, but it is recommendable to use unique name by case, to facilitate human communication.
tags: an ordered list of words, used to classify the cases as a tree (in case of select this kind of view). Tags could be also used to filter tags (a case with all its tags sets as disabled will be hidden)
help: a short description remarking why is interesting this case
owner: e-mail of the person responsible of this case (in the future the application could send them e-mails in case of errors)
GiD batch: specifying that is a GiD batch it is not necessary to fill so much fields like for a general case (exe, args, outfile, readingproc, filetosource, codetosource)
batch: the most important information is the name (relative) of the batch to run by GiD
checks: a collection of one or more conditionals that must be true to pass the test (buttons + and - allow to add/delete checks)
Check
Button to delete cases:
This button deletes the selected cases. Only its definition is deleted, the batch file and models remain intact.
Button to save project
If something has changed (cases, last test results or preferences) the current information is save in its respective files.
When exiting the program, in case of changes it will ask to save or lost them.
Button to show/edit a batch file
...