Opened image in memory
Posted: Sat Oct 21, 2017 12:15 pm
Hi,
I have an issue with how XnView MP seems to keep an opened image in memory and doesn't update it when the image is modified in another program.
XnView classic didn't do that.
So, say I double click and image to view it in fullscreen which opens it in a tab (for god knows what reason) and then I modify it in Photoshop... when I get back to XnView and double click on it again it's just like it was before. The only way to get it to work is to either double-click on another image and then back to the modified image or press Ctrl-R to reload it.
Why doesn't it reload automatically and where can I set it to do that if possible at all?
And what's the purpose of not being able to disable tabs? I don't need them. I can't imagine any reason as to why I'd want it to keep a ton of images in memory. I set it to have a maximum of 1 tab, but that 1 tab still remains open after I go back to the browser from fullscreen. Why? Why is this not optional?
I have an issue with how XnView MP seems to keep an opened image in memory and doesn't update it when the image is modified in another program.
XnView classic didn't do that.
So, say I double click and image to view it in fullscreen which opens it in a tab (for god knows what reason) and then I modify it in Photoshop... when I get back to XnView and double click on it again it's just like it was before. The only way to get it to work is to either double-click on another image and then back to the modified image or press Ctrl-R to reload it.
Why doesn't it reload automatically and where can I set it to do that if possible at all?
And what's the purpose of not being able to disable tabs? I don't need them. I can't imagine any reason as to why I'd want it to keep a ton of images in memory. I set it to have a maximum of 1 tab, but that 1 tab still remains open after I go back to the browser from fullscreen. Why? Why is this not optional?