Thanks for the 0 Byte file fix in the beta! But there is still a wrong behaviour left. Description:
Start browser, go to where the 0 Byte file is located. Double-click the 0 Byte mini-pic symbol. As expected the warning message >Error opening...< comes up. Click ok.
Now a second instance of XnView is started with a different path! That should obviously not happen.
0 Byte file fix
Moderators: XnTriq, helmut, xnview
-
- Author of XnView
- Posts: 45307
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
Re: 0 Byte file fix
Can't reproducepic_viewer wrote:Thanks for the 0 Byte file fix in the beta! But there is still a wrong behaviour left. Description:
Start browser, go to where the 0 Byte file is located. Double-click the 0 Byte mini-pic symbol. As expected the warning message >Error opening...< comes up. Click ok.
Now a second instance of XnView is started with a different path! That should obviously not happen.

Pierre.
-
- Posts: 251
- Joined: Sat Nov 17, 2007 7:53 am
- Location: Germany
-
- Posts: 8705
- Joined: Sun Oct 12, 2003 6:47 pm
- Location: Frankfurt, Germany
-
- Author of XnView
- Posts: 45307
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
I can't reproduce this bug.helmut wrote:Confirmed.![]()
Details:
Windows XP SP2, file 'Null Byte.jpg' with 0 bytes, JPG files are associated with XnView 1.93 beta.
With a clean .ini, jpg is associated with xnview, i double click on the 0 byte jpeg, and i have the error box, and xnview. No other instance
Pierre.
-
- Posts: 251
- Joined: Sat Nov 17, 2007 7:53 am
- Location: Germany
That sounds like you did not do what I wrote above. Second step is to again click on the 0 Byte file from within the browser.xnview wrote:I can't reproduce this bug.helmut wrote:Confirmed.![]()
Details:
Windows XP SP2, file 'Null Byte.jpg' with 0 bytes, JPG files are associated with XnView 1.93 beta.
With a clean .ini, jpg is associated with xnview, i double click on the 0 byte jpeg, and i have the error box, and xnview. No other instance
-
- Author of XnView
- Posts: 45307
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
Oh ok, it's because you have 'open action' for other file on 'open in associate program', right? The dialog box is from the second instancepic_viewer wrote:That sounds like you did not do what I wrote above. Second step is to again click on the 0 Byte file from within the browser.xnview wrote:I can't reproduce this bug.helmut wrote:Confirmed.![]()
Details:
Windows XP SP2, file 'Null Byte.jpg' with 0 bytes, JPG files are associated with XnView 1.93 beta.
With a clean .ini, jpg is associated with xnview, i double click on the 0 byte jpeg, and i have the error box, and xnview. No other instance
Pierre.
-
- Posts: 251
- Joined: Sat Nov 17, 2007 7:53 am
- Location: Germany
Sorry, I don't understand. But I think the error is somewhat caused already by XnView's basic behaviour. If I try to open an invalid file from an external program (like TC), and XnView can not open that file (Error message shown), why is it started at all and not closed automatically again? I bet that then the 'second instance start' from within the browser would not happen too.xnview wrote:Oh ok, it's because you have 'open action' for other file on 'open in associate program', right? The dialog box is from the second instance
-
- Author of XnView
- Posts: 45307
- Joined: Mon Oct 13, 2003 7:31 am
- Location: France
It's the behaviour of xnview... So yes i think that xnview must be closed!pic_viewer wrote:Sorry, I don't understand. But I think the error is somewhat caused already by XnView's basic behaviour. If I try to open an invalid file from an external program (like TC), and XnView can not open that file (Error message shown), why is it started at all and not closed automatically again?xnview wrote:Oh ok, it's because you have 'open action' for other file on 'open in associate program', right? The dialog box is from the second instance
Pierre.
-
- Posts: 251
- Joined: Sat Nov 17, 2007 7:53 am
- Location: Germany