Sure:xnview wrote: Only when you have this setting, very strange. Could you tell me which sort setting do you have in the browser?
here it's
I guess that lists all the setings I have.
Cache slows down viewing
Moderators: helmut, XnTriq, xnview
-
Guest
Could you send me a PM, i would like to send you a beta version?Anonymous wrote:Sure:xnview wrote: Only when you have this setting, very strange. Could you tell me which sort setting do you have in the browser?
here it's
I guess that lists all the setings I have.
Pierre.
-
klaus2
Hi Pierre,
i'm very interested in the solution too.
I think there are two (already mentioned) issues connected.
a) If you set "read one image ahead" and keep pgdown pressed in the viewer, you'll see your viewer stay on the current image and you'll see (caption; status bar) that at the same time all subsequent images are read in the background (without being shown), what obviously does not make sense.
That is true at least on win98 (maybe opsys-specific ?)
Obviously the "nexe image ahead" should been shown before processing the next-next-next one ... and so on
b) The other issue/thread is that you should be able to cancel a paint operation when meanwhile another image is requested eg. be pressing pgdown (go on to next one).
So obviously there is a conflict when constantly keep the pgdown pressed: show next image and cancel that show.
Imo that is a timing problem: Try to paint the next image; but when within a certain time period the pgdown message arrives, cancel the paint and proceed with the subsequent image ...
Am i understandable and does this make sense?
Best Regards!
klaus2
i'm very interested in the solution too.
I think there are two (already mentioned) issues connected.
a) If you set "read one image ahead" and keep pgdown pressed in the viewer, you'll see your viewer stay on the current image and you'll see (caption; status bar) that at the same time all subsequent images are read in the background (without being shown), what obviously does not make sense.
That is true at least on win98 (maybe opsys-specific ?)
Obviously the "nexe image ahead" should been shown before processing the next-next-next one ... and so on
b) The other issue/thread is that you should be able to cancel a paint operation when meanwhile another image is requested eg. be pressing pgdown (go on to next one).
So obviously there is a conflict when constantly keep the pgdown pressed: show next image and cancel that show.
Imo that is a timing problem: Try to paint the next image; but when within a certain time period the pgdown message arrives, cancel the paint and proceed with the subsequent image ...
Am i understandable and does this make sense?
Best Regards!
klaus2
But i'm not sure that current problem is that...-
xasx
Same problem here, especially with pdfs and many jpgs in folder. One thing could be that XnView shows the numer of image files in the viewer window (e.g. "7/500"), so it must enumerate all the images. Since i do not know implementation details, it is too speculative to say that XnView could check the file content against the extension (*) or build the thumbnail somewhere to put it in the cache.
(*) That would mean that XnView while enumerating files in current folder checks the content of each file. This process would additionally be slowed down by an on-access virus scanner.
Many speculations...
Greetz,
Andy.
(*) That would mean that XnView while enumerating files in current folder checks the content of each file. This process would additionally be slowed down by an on-access virus scanner.
Many speculations...
Greetz,
Andy.
-
bottom
bump!
problem not solved till version 1.91.4
...sorry, have created another thread yesterday
http://newsgroup.xnview.com/viewtopic.php?p=52611
problem not solved till version 1.91.4
...sorry, have created another thread yesterday
http://newsgroup.xnview.com/viewtopic.php?p=52611