Ensure export file path always contains a valid file name extension #1736
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
|
Argh you’re right I completely forgot about that one. I’ll take another look to see what’s needed for that one to move forward. |
J5lx
force-pushed
the
fixes/export-suffix
branch
from
dd70c9a
to
bdb6dfd
Compare
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.
On Windows, it is possible to select an export file path with an invalid file name extension by manually typing the name of a pre-existing file into the text field. That will then confuse the movie exporter because it doesn’t know how to handle the unknown extension, as seen in this forum thread. To avoid this, it is necessary to manually check the extension of the selected file path.