Skip to content
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.

Sign up for GitHub

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

Jump to bottom

{tag} as folder name in "Export As" creating nested folders after first Export #4059

Open
Brandelan opened this issue Sep 22, 2023 · 4 comments · May be fixed by #4389
Open

{tag} as folder name in "Export As" creating nested folders after first Export #4059

Brandelan opened this issue Sep 22, 2023 · 4 comments · May be fixed by #4389
Assignees
@gui-marc
Labels
bug medium priority time-2
Milestone
v1.3.x

Comments

@Brandelan
Copy link

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

  • Aseprite version: v1.3-rc6-x64 Steam/beta/
  • System: Windows
@Gasparoken Gasparoken added this to the v1.3.x milestone Sep 26, 2023
@Gasparoken Gasparoken self-assigned this Sep 26, 2023
@Gasparoken
Copy link
Member

Thanks for reporting this. I was able to reproduce it.

@gui-marc
Copy link

Hello guys. I want to solve this bug, can I be assigned to this issue?

@dacap
Copy link
Member

dacap commented Feb 26, 2024

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).

@dacap dacap assigned gui-marc and unassigned Gasparoken Feb 26, 2024
gui-marc added a commit to gui-marc/aseprite that referenced this issue Mar 25, 2024
@gui-marc
Show format within filename when exporting file
ad7c8ee 
- 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
@gui-marc
Show format within filename when exporting file
1cead6d 
- 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
@gui-marc
Show format within filename when exporting file
4783f3b 
- 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 gui-marc linked a pull request Mar 28, 2024 that will close this issue
Open
@gui-marc
Copy link

gui-marc commented May 5, 2024 •
edited

Hi guys! Can someone please review my PR for this issue? This fix would be useful for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gui-marc gui-marc

Labels
bug medium priority time-2
Projects
Aseprite v1.3.x
Status: No status
Milestone
v1.3.x
Development

Successfully merging a pull request may close this issue.

Show format within filename when exporting file gui-marc/aseprite
4 participants
@dacap @Brandelan @Gasparoken @gui-marc