0.75: Going back to XnView Classic because...
Posted: Fri Oct 02, 2015 1:34 pm
Hi, I found 3 bugs/differences with XNView with the Windows version that interrupt my work flow too much so I'm going to go back, but I thought I would report them. Hopefully they're all bugs to be fixed.
1. I use View->Filter By->Custom to hide my .CR2 (Raw) files. Each photo I take has a JPEG and a RAW, I don't use the RAWs in XnView, so I hide them by default, but they're in the file system. In the full screen viewer, if I delete the JPG, the .CR2 will show up next. Deleting doesn't respect the Custom filter. If I just Page down or Page up, the custom filter works as intended. This works correctly in XnView.
2. I use Zoom->Fit Image to Window and image resizing is not as good in XNViewMP. It's common to see high contrast areas almost look like they were linearly scaled without any sampling, with obvious scaling artifacts present in faces, rather than a smooth transition. In an image viewer, the image must look it's best. I couldn't see anything that might indicate some hardware acceleration might be present, so I'll assume it was XNViewMP responsible.
3. If I turn Zoom Lock on, and press *, then Page up and down to compare shots, it works as expected. If I press / for Fit to Window, Zoom Lock turns itself off. This wasn't the case in XNView. I compare a lot of burst shots so I jump between 100% and Fit to Window, and it's a pain that Zoom Lock keeps turning off.
XnViewMP
Version 0.75 x64 (Sep 21 2015)
1. I use View->Filter By->Custom to hide my .CR2 (Raw) files. Each photo I take has a JPEG and a RAW, I don't use the RAWs in XnView, so I hide them by default, but they're in the file system. In the full screen viewer, if I delete the JPG, the .CR2 will show up next. Deleting doesn't respect the Custom filter. If I just Page down or Page up, the custom filter works as intended. This works correctly in XnView.
2. I use Zoom->Fit Image to Window and image resizing is not as good in XNViewMP. It's common to see high contrast areas almost look like they were linearly scaled without any sampling, with obvious scaling artifacts present in faces, rather than a smooth transition. In an image viewer, the image must look it's best. I couldn't see anything that might indicate some hardware acceleration might be present, so I'll assume it was XNViewMP responsible.
3. If I turn Zoom Lock on, and press *, then Page up and down to compare shots, it works as expected. If I press / for Fit to Window, Zoom Lock turns itself off. This wasn't the case in XNView. I compare a lot of burst shots so I jump between 100% and Fit to Window, and it's a pain that Zoom Lock keeps turning off.
XnViewMP
Version 0.75 x64 (Sep 21 2015)