Jump to content

Two Bugs: v2.72 pdn file won't open; program fails quitting


entY8

Recommended Posts

The opening of this file aborts with "There was an unspecified error while opening the file." It was created with the old version 2.72 contains two layers and is 440x260 in size. I have another pdn file created exactly the same way (with slightly different content though) which I created at the same time (with version 2.72 too) which is still working now. (I can post that one too if you're interested in it)

The other bug I ran over: when closing the program a very short time (within a second or something) after starting it via opening an image in an explorer window, it doesn't quit properly and a dead non-responsive "PaintDotNet.exe" remains in the task manager; there is no program window visible.

This results in the problem, that you can't open more instances of the program, since they all detect the existing process (probably pass the information of the image to be opened to it; though you don't see any effect of that) and then quit themselves again. I have to manually shoot the dead process in order to be able to open new program instances again.

Link to comment
Share on other sites

Well, I would say it's only sort of "your fault" ... I wish the dialog could be made a little more intelligent about file extensions but unfortunately I don't have control over it. It's a built-in Windows dialog. Maybe the new stuff in Vista will give me the correct amount of control so that we can make it less easy to save as a file type with the wrong file extension.

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to comment
Share on other sites

When it gets to open a file with a different encoding inside than advertised in the extension, it should act like Windows Media Player does with movies; the best case that would be. It should tell the user that the contained file format and the file extension don't match and ask if it should try to open it anyway. Maybe the program should even detect the encoding before asking so it can tell the user what the correct extension would be too. (That'd would have helped in my case a lot :P)

About the saving dialog... as we are talking about pictures it really rarely happens that one would want to save a picture with a wrong file name extension (as opposed to saving text files with notepad for example). Maybe you should just force the correct extension for the file after retrieving the path desired by the user from the Windows dialog. (in this case: append ".png", since the filename didn't end with ".png" (namely with ".pdn" instead); then my file would have been called "2f.pdn.png" and i would have found my mistake quickly :wink:)

btw, this saving mistake occurred to me could really be annoying if you overwrote the pdn file you wanted to keep for later reuse (in my case i didn't really care about it so it didn't matter :P)

Link to comment
Share on other sites

Well...

Paint.NET does not have a system in place for "auto-detection" of file formats regardless of file name extension. Reason for this is that we currently rely on a lot of GDI+/.NET code and it doesn't have a method for doing this. Well, it does this internally but it isn't available for Paint.NET's use and querying.

Because of this it's not currently possible to determine if a file is invalid because it's the wrong type (but otherwise "valid"), or if the file is actually corrupt.

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to comment
Share on other sites

  • 3 weeks later...

just for your information: the bug which causes the program to fail quitting and leave a dead PaintDotNet.exe process behind, so that new images can't be opened before this process is killed, is still existing in the current version (beta 1 build 3.0.2525.34975).

Link to comment
Share on other sites

just for your information: the bug which causes the program to fail quitting and leave a dead PaintDotNet.exe process behind, so that new images can't be opened before this process is killed, is still existing in the current version (beta 1 build 3.0.2525.34975).

I have not been able to reproduce this. I will need to good, exact, step-by-step instructions that reproduce the problem.

The Paint.NET Blog: https://blog.getpaint.net/

Donations are always appreciated! https://www.getpaint.net/donate.html

forumSig_bmwE60.jpg

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...