Pli checker #37
Merged
Pli checker #37
Conversation
This file contains 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.
Solved the identified bugs.
The user has now the possibility to define the validation function at the instantiation of the
EntryVariableclass. The validation is now triggered each time a text is inserted in the entry widget.The validation consists of the two required steps, the checking of the extension and of the file existence.
If the validation passes, a new event is triggered followed by the retrieval of the information from the input
.plifile.After reading the
.plifile, the initial and output folders are updated accordingly, no matter the.plifile path is entered manually or not.