Optional functionality to annotated in order #10
Conversation
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
1 participant
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.
At the moment, there aren't any options to traverse the target directory in different orders. I was using this tool to annotate PNG files named: file_1, file_2, ... , frame_10, frame_11, etc. I found it useful to have the files displayed for annotating in a more intuitive order rather than frame_1, frame_10, frame_11, etc. Maybe others will find this useful as well.
The original functionality can be maintained by not including the extra command line arguments. I have added these instructions to the README file.
I also made some minor formatting changes to that my linter (flake8) did not raise any errors.