This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Add zero padding to otio burnins for "current_frame" #2423
Merged
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
jakubjezek001
approved these changes
Dec 20, 2021
There was a problem hiding this comment.
Hey Jerome, thank you very much for your participation. The change works well. BTW this already gives me an idea to extend upon it to add padding to all numbers.
I remember that someone recently mentioned that it would be cool if we supported an Anatomy way of padding formatting - for example {frame_start:0>7} as 0000991. Just an idea but not really not that important.
Anyway thanks and enjoy the holidays ;)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Currently the option the "current_frame" option for burnins is not padded
This cause the text box to move with the current frame length increasing