-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{tag} as folder name in "Export As" creating nested folders after first Export #4059
Comments
Thanks for reporting this. I was able to reproduce it. |
Hello guys. I want to solve this bug, can I be assigned to this issue? |
hi @gui-marc, sure, I can assign you this issue, remember to sign the CLA document you might have received in your email address (from signNow). |
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Mar 25, 2024
- Exposed path_formats defined in filename_formatter and changed type from vector to array increasing performance. - While setting the output filename in the export file window, considered path formats (e.g. {tag}, {frame}) to also be included in the filename. Resolves aseprite#4059
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Mar 27, 2024
- Exposed path_formats defined in filename_formatter and changed type from vector to array increasing performance. - While setting the output filename in the export file window, considered path formats (e.g. {tag}, {frame}) to also be included in the filename. Resolves aseprite#4059
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Mar 27, 2024
- Exposed path_formats defined in filename_formatter and changed type from vector to array increasing performance. - While setting the output filename in the export file window, considered path formats (e.g. {tag}, {frame}) to also be included in the filename. Resolves aseprite#4059
Hi guys! Can someone please review my PR for this issue? This fix would be useful for me |
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Jun 2, 2024
- When exporting a file, if the file was already saved, show the relative path to the original saved file. Resolves aseprite#4059
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Jun 3, 2024
- When exporting a file that was already saved, shows the relative path to the original path instead of only the filename. Resolves aseprite#4059
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Jun 3, 2024
- When exporting a file that was already saved, shows the relative path to the original path instead of only the filename. Resolves aseprite#4059
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Jun 3, 2024
- When exporting a file that was already saved, shows the relative path to the original path instead of only the filename. Resolves aseprite#4059
gui-marc
added a commit
to gui-marc/aseprite
that referenced
this issue
Jun 3, 2024
- When exporting a file that was already saved, shows the relative path to the original path instead of only the filename. Resolves aseprite#4059
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your bug report or feature request here
If you go to "Export As" and use {tag}/0001.png for example as your file name, it works as expected, creating a folder w/ the name of whatever the tag is.
However, if you export again, the original {tag}/ you wrote is no longer there in the autofilled export name, but it seems like aseprite still treats it as if it is there. So if you then write {tag}/0001.png again, it will export to {tag}/{tag}/0001.png.
All subsequent exports will be exported in this manner, and isn't able to be changed. Even closing and re-opening the project does not fix it.
Aseprite and System version
The text was updated successfully, but these errors were encountered: