See here:
http://newsgroup.xnview.com/viewtopic.php?t=4422
I confirm.
To reproduce:
b2, delete ini.
Go to directory with many big images. Select image & press F11.
Now quickly press PgDown multiple times. Image loading is not interrupted and it should.
Also, after stopping pressing PgDown you can see keypresses still processed by XnView (a few next images are displayed).
X.
b2: problem with loading images in separate thread
Moderators: XnTriq, helmut, xnview
Re: b2: problem with loading images in separate thread
If you disabled "High quality', do you have always the problem?Xyzzy wrote:See here:
http://newsgroup.xnview.com/viewtopic.php?t=4422
I confirm.
To reproduce:
b2, delete ini.
Go to directory with many big images. Select image & press F11.
Now quickly press PgDown multiple times. Image loading is not interrupted and it should.
Also, after stopping pressing PgDown you can see keypresses still processed by XnView (a few next images are displayed).
With or without 'Read ahead'?
Pierre.
OK... I believe I was able to get "something" (and setting View>'High zoom quality' or 'Cache Read Ahead' didn't change anything...).
In Fullscreen, if you keep pressing PgDown on large images, you will actually skip the image AFTER the one being loaded... (the one being loaded will be fully loaded and displayed).
So: XnView is loading 1. You press 'next' => XnView continues to load 1 and will display 1, but will skip 2. It will then directly load and display 3.
This is not what I expected...
I hoped for the possibility to interrupt the current loading of image:
XnView is loading 1. You press 'next' => XnView immediately stops loading 1 and display what has been loaded so far of 1, before proceeding to 2.
Would this last behaviour be possible, Pierre?
Olivier
In Fullscreen, if you keep pressing PgDown on large images, you will actually skip the image AFTER the one being loaded... (the one being loaded will be fully loaded and displayed).
So: XnView is loading 1. You press 'next' => XnView continues to load 1 and will display 1, but will skip 2. It will then directly load and display 3.
This is not what I expected...
I hoped for the possibility to interrupt the current loading of image:
XnView is loading 1. You press 'next' => XnView immediately stops loading 1 and display what has been loaded so far of 1, before proceeding to 2.
Would this last behaviour be possible, Pierre?
Olivier
Do you have tested in beta 3? Loading is interupted!Olivier_G wrote:OK... I believe I was able to get "something" (and setting View>'High zoom quality' or 'Cache Read Ahead' didn't change anything...).
In Fullscreen, if you keep pressing PgDown on large images, you will actually skip the image AFTER the one being loaded... (the one being loaded will be fully loaded and displayed).
So: XnView is loading 1. You press 'next' => XnView continues to load 1 and will display 1, but will skip 2. It will then directly load and display 3.
This is not what I expected...
I hoped for the possibility to interrupt the current loading of image:
XnView is loading 1. You press 'next' => XnView immediately stops loading 1 and display what has been loaded so far of 1, before proceeding to 2.
Would this last behaviour be possible, Pierre?
Pierre.
Well, I have tested now and I have mixed feelings.
I tested with 2-2.5MB JPEGs. If I press PageDown ten times in about 3 seconds, after last press there are still approx. 2 image skips to next picture.
I wonder if it may be caused by the way Windows processes keypress messages when under load (images are rendered), delivering them to application with some delay???
X.
I tested with 2-2.5MB JPEGs. If I press PageDown ten times in about 3 seconds, after last press there are still approx. 2 image skips to next picture.
I wonder if it may be caused by the way Windows processes keypress messages when under load (images are rendered), delivering them to application with some delay???
X.
Yes i think, i'll try to fix itXyzzy wrote:Well, I have tested now and I have mixed feelings.
I tested with 2-2.5MB JPEGs. If I press PageDown ten times in about 3 seconds, after last press there are still approx. 2 image skips to next picture.
I wonder if it may be caused by the way Windows processes keypress messages when under load (images are rendered), delivering them to application with some delay???
Pierre.