Page 3 of 4

Re: "Must fixes" for next release

Posted: Mon Nov 29, 2010 4:07 pm
by marjoleink
Rationale for 'must fix': important existing meta data is destroyed.

IPTC: Updating XMP destroys some of it

Marjolein Katsma

Re: "Must fixes" for next release

Posted: Sun Dec 12, 2010 10:54 pm
by Tommy
does anybody know when next XnView version will be released for beta testing?

will it be numbered as XnView 1.98 ?

Re: "Must fixes" for next release

Posted: Mon Dec 13, 2010 11:49 am
by xnview
Tommy wrote:does anybody know when next XnView version will be released for beta testing?
will it be numbered as XnView 1.98 ?
Development of 1.98 will start in january...

Re: "Must fixes" for next release

Posted: Mon Dec 13, 2010 12:02 pm
by Tommy
thanks :)

Re: "Must fixes" for next release

Posted: Sun Dec 26, 2010 4:02 pm
by Origami
Certainly a very nice to have for me - Problems reading (and possibly saving) jpeg2000 format. See original thread. I also get a read error 'Unknown Format' in VBScript so it's not just VB6 but the scripting runtime also - probably ASP as well. I'm running XP Home SP2 if that is a factor. Everything else works fantastic so I'd have to change imaging libraries just to get jpeg2000 support.

Re: "Must fixes" for next release

Posted: Sun Jan 09, 2011 6:49 am
by xnvi
Submitting this as "must fix" under the rationale that "The users' images are endangered (changed, deleted, ...)"

"Synchronize Browser selection with current View" broken

In the second post on that page I describe how this problem resulted in images I wanted to keep being accidentally deleted. In my opinion, there is a very high potential for XnView users to permanently delete images unknowingly.

Re: "Must fixes" for next release

Posted: Mon May 09, 2011 1:50 pm
by Gemorroj
filename "a4yowq6kbnf1.jpg (443×457).jpg"
open file - crash

Re: "Must fixes" for next release

Posted: Fri May 27, 2011 4:23 am
by marsh
Most of these are fixed. ;) Reset topic?

Re: "Must fixes" for next release

Posted: Fri May 27, 2011 4:32 am
by Tommy
+1

Re: "Must fixes" for next release

Posted: Mon May 30, 2011 7:32 am
by xnview
marsh wrote:Most of these are fixed. ;) Reset topic?
yes, i think...

Re: "Must fixes" for next release

Posted: Fri Aug 19, 2011 2:29 am
by eagleeyez
There is an issue with saving bitmap file introduced in the latest version, I hope it will be fixed in the next release.

Re: "Must fixes" for next release

Posted: Thu Feb 09, 2012 6:16 am
by marsh
bump

Re: "Must fixes" for next release

Posted: Sun May 13, 2012 3:09 am
by xnvi
Hi,

I'd like to submit this issue again as "must fix" again under the rationale that "users' images are endangered (changed, deleted, ...)"

"Synchronize Browser selection with current View" broken

There is a very high potential for XnView users to permanently delete images unknowingly. I am sure I have lost numerous images as a result of this problem.

Re: "Must fixes" for next release

Posted: Sun Aug 19, 2012 10:35 am
by AlexL
I'd like to add to "must fixes" a bug described here:
XnView can't save a bitmap file as raw file correctly
because I have the same problem (though I have it in NConvert, and not in XnView): conversion to raw RGB format does not work. It saves only one component instead of three components.
Hence I have to use older version of NConvert.

Re: "Must fixes" for next release

Posted: Thu Nov 15, 2012 3:29 am
by xnvi
Hi,

I'm using version 1.99.5, and just want to point out that this bug that can easily cause the wrong files to be deleted is still present:
"Synchronize Browser selection with current View" broken

To summarize:

"Dual monitor. Use second monitor (Browser & Slideshow)" - On
"Synchronize Browser selection with current View" - On
"Mouse Wheel" - "Previous/Next file"
"Confirm file delete" - Off
"Go to next image when deleting current" - On

Double-click on a thumbnail in the browser. The image opens in fullscreen on the other monitor. Move the mouse cursor over to the fullscreen view without clicking and mousewheel up/down to view different images in the folder. At some eventual image, press Delete to delete the image currently being viewed. The image disappears and the next image gets shown, giving the user apparent confirmation that the one they were just looking at when they pressed Delete got removed. In fact, the image that they think they deleted was not deleted, and they actually unknowingly deleted the wrong image.

The problem is that the "Synchronize Browser selection with current View" feature is simply not working in this situation. The mousewheel up/down in the fullscreen view shows the previous/next image as expected but fails to keep the browser selection in sync with the current fullscreen view.

Hope this can be fixed in an upcoming release. Thanks for the great software!