XnView Software

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.

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

Can't reproduce With a clean .ini, do you have it?

Yes, even with clear (new/fresh) ini. Second instance starts with the last used path (as soon as you have an ini).

When using context menu "Open" the problem does not occur. (Perhaps something to do with the double-click?).

Confirmed.

Details:
Windows XP SP2, file 'Null Byte.jpg' with 0 bytes, JPG files are associated with XnView 1.93 beta.

helmut wrote:Confirmed.

Details:
Windows XP SP2, file 'Null Byte.jpg' with 0 bytes, JPG files are associated with XnView 1.93 beta.

I can't reproduce this bug.
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

xnview wrote:

helmut wrote:Confirmed.

Details:
Windows XP SP2, file 'Null Byte.jpg' with 0 bytes, JPG files are associated with XnView 1.93 beta.

I can't reproduce this bug.
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

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.

pic_viewer wrote:

xnview wrote:

helmut wrote:Confirmed.

Details:
Windows XP SP2, file 'Null Byte.jpg' with 0 bytes, JPG files are associated with XnView 1.93 beta.

I can't reproduce this bug.
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

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.

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

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

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.

pic_viewer wrote:

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

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?

It's the behaviour of xnview... So yes i think that xnview must be closed!

Works perfectly in Beta 2 now!