Page 1 of 1
Memory leak when using the double-click feature
Posted: Mon Jan 03, 2005 2:41 pm
by Olivier_G
Hi,
I have just noticed that memory of images (current, and eventually of ahead/previous cache) is not released when going back from 'View' (normal or full screen) to browsing with the
double-click feature.
A
?
Added: To be precise, it is never released (aka: a leak), even when viewing other images...
Olivier
PS: I use XnView 1.74 on Windows XP+SP2
Re: Memory leak when using the double-click feature
Posted: Tue Jan 04, 2005 7:28 am
by xnview
Olivier_G wrote:I have just noticed that memory of images (current, and eventually of ahead/previous cache) is not released when going back from 'View' (normal or full screen) to browsing with the
double-click feature.
A
?
Added: To be precise, it is never released (aka: a leak), even when viewing other images...
It's normal, because view is not closed. You can take a look at the menu "Window".
Re: Memory leak when using the double-click feature
Posted: Tue Jan 04, 2005 9:34 am
by helmut
xnview wrote:It's normal, because view is not closed. You can take a look at the menu "Window".
Think like Olivier and other people I find this behaviour surprising.
I expected the current image to be closed when double-clicking on it.
Sure enough the option in Options > View " says "Double-click to open Browser", not "Double-click to close view", so the current behaviour is correct, but I wonder whether this is really useful and what people need and expect.
Re: Memory leak when using the double-click feature
Posted: Tue Jan 04, 2005 10:07 am
by xnview
helmut wrote:xnview wrote:It's normal, because view is not closed. You can take a look at the menu "Window".
Think like Olivier and other people I find this behaviour surprising.
I expected the current image to be closed when double-clicking on it.
Sure enough the option in Options > View " says "Double-click to open Browser", not "Double-click to close view", so the current behaviour is correct, but I wonder whether this is really useful and what people need and expect.
So what is better. When "Only one view" + "double click to open ..." must close all view before to return to the browser?
Re: Memory leak when using the double-click feature
Posted: Tue Jan 04, 2005 10:22 am
by helmut
xnview wrote:...
So what is better. When "Only one view" + "double click to open ..." must close all view before to return to the browser?
I would expect that the current view (the one you double-click onto) is closed and the browser is opened. All the other views should not be affected.
Re: Memory leak when using the double-click feature
Posted: Tue Jan 04, 2005 12:29 pm
by Olivier_G
xnview wrote:It's normal, because view is not closed. You can take a look at the menu "Window".
Doh!
Right! I didn't even think about it due to the "Only one view" feature...
helmut wrote:xnview wrote:So what is better. When "Only one view" + "double click to open ..." must close all view before to return to the browser?
I would expect that the current view (the one you double-click onto) is closed and the browser is opened. All the other views should not be affected.
This one looks like a winner...
Olivier
Re: Memory leak when using the double-click feature
Posted: Tue Jan 04, 2005 2:01 pm
by Dreamer
Olivier_G wrote:helmut wrote:xnview wrote:So what is better. When "Only one view" + "double click to open ..." must close all view before to return to the browser?
I would expect that the current view (the one you double-click onto) is closed and the browser is opened. All the other views should not be affected.
This one looks like a winner...
Another vote for that.
Also "Only one view" + "double click to open ..." options shoud be turned on by default, because (probably) most users expect it...