-
-
Notifications
You must be signed in to change notification settings - Fork 7k
Save path for never-previously-saved Workspaces defaults to the Desktop. #3996
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
Comments
Related to #3979 for the save case. |
Gasparoken
added a commit
to Gasparoken/aseprite
that referenced
this issue
Aug 30, 2023
…ite#3996) This regression was added in 1.3rc5. Every time you wanted to save a new sprite the dialog would start at the root path instead of the last used directory location.
Gasparoken
added a commit
to Gasparoken/aseprite
that referenced
this issue
Aug 30, 2023
…ite#3996) This regression was added in 1.3rc5. Every time you wanted to save a new sprite the dialog would start at the root path instead of the last used directory location.
Gasparoken
added a commit
to Gasparoken/aseprite
that referenced
this issue
Sep 13, 2023
…prite#3996) Regression added in 056073b in the custom file selector. Every time you saved a new sprite the dialog started at the root path (e.g. Desktop) instead of the last used directory.
dacap
pushed a commit
that referenced
this issue
Sep 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever I create a new Document and save it for the first time, the default save path is my Desktop. I have never saved anything directly to the Desktop with ASEprite, and navigating to my usual save folders adds several (admittedly trivial) steps to my Save As experience.
This, I find undesirable.
Like, wow, substantially more undesirable than I would have imagined; I am actually genuinely surprised at how extremely deeply undesirable I have been finding it, hoo-whee mang it is a bad scene. :V
Other users with this version have shared discovery of this weird bug as well, and have been similarly frustrated.
Version 1.3-rc5-x64, nor any previous version to my memory, ever did this, and I find myself wondering why it might have started.
In all cases, please fix it, and thank you for looking into it! ;0; <3
..using ASEprite v.1.3-rc6-x64 on Win10.
The text was updated successfully, but these errors were encountered: