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.

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

New File > Save As Crash #143

Closed
aseprite-bot opened this issue Aug 20, 2014 · 4 comments
Closed

New File > Save As Crash #143

aseprite-bot opened this issue Aug 20, 2014 · 4 comments

Comments

@aseprite-bot
Copy link
Collaborator

From zvord...@gmail.com on July 17, 2012 20:46:10

What steps will reproduce the problem? 1. Open ASEPRITE
2. File > New
3. File > Save/Save As What is the expected output? What do you see instead? Expect "save file" window. Instead the process dies without any error message. What version of the product are you using? On what operating system? 0.9.3 - Windows XP Pro 32-bit
Problem does not happen with 0.9.2

Original issue: http://code.google.com/p/aseprite/issues/detail?id=143

@aseprite-bot aseprite-bot added this to the v0.9 milestone Aug 20, 2014
@aseprite-bot
Copy link
Collaborator Author

From davidcapello on July 17, 2012 18:13:31

I've found where the problem is, but I don't know why it's happening in your case (maybe a path to a deleted folder is in your aseprite.ini, but that shouldn't crash the program). Anyway I'll try to release 0.9.4 with the fix. Also, you can try to remove aseprite.ini file to check if the problem disappear.

Commit: dacap@b090629

Status: Fixed
Owner: davidcapello
Labels: -Priority-Medium Priority-Critical Milestone-0.9

@aseprite-bot
Copy link
Collaborator Author

From zvord...@gmail.com on July 17, 2012 18:24:59

That worked. Thanks!

I'm not sure if it is related, but I set ase files to open by default with
the 0.9.2 Aseprite exe and then downloaded 0.9.3 to a new folder and tried
to set that exe as the default program for ase files and it would not work
until I renamed the 0.9.3 exe. Maybe renaming the exe contributed to the
problem? Probably not but not sure.

@aseprite-bot
Copy link
Collaborator Author

From davidcapello on August 23, 2012 17:50:59

Issue #149 has been merged into this issue.

@aseprite-bot
Copy link
Collaborator Author

From davidcapello on August 23, 2012 20:20:08

Issue #162 has been merged into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant