Posted: Wed Sep 14, 2005 8:23 am
but i would suggest to make it optional, because if you ask ten people you'll have ten favorite approachs ..
Various discussion boards for XnView and related products
https://newsgroup.xnview.com/
Yesklaus2 wrote:but i would suggest to make it optional, because if you ask ten people you'll have ten favorite approachs ..
Actually, I can't imagine someone who would want XnView not to respond when pressing a key to move to next file before the end of display. It is almost like a program 'freeze'...klaus2 wrote:but i would suggest to make it optional, because if you ask ten people you'll have ten favorite approachs ..
i agree. a loading time would be good too, after the progress bar is full.klaus2 wrote: PS: and I support the suggestion to show a 'progress bar'(and/or number) to show the status for caching images...
i agree. not bad ideaPS: and I support the suggestion to show a 'progress bar'(and/or number) to show the status for caching images...
I just got a feedback (in french) from someone who tried XnView and found it too "slow" (probably when navigating with Viewer... -> this very issue). The problem is not that he found it too slow... the problem is that for one who say so, hundreds of people just try and put XnView aside for a long time without saying anything...Olivier_G wrote:Right: I think this the most important performance issue in XnView right now (and probably a 'stopper' for a lot of people).ali wrote:Again, i don't know how they do it in acdsee - you can scroll from picture to picture without delays. in xnview, you have to wait until the whole picture is in cache.
In acdsee, you don't have to wait for that process, you can "fly through" the pictures to the last one you want to see. i mean, the picture will show partially, so you know where you are in directory and you don't have to wait for that slow caching process (llama's opinion:)
=> XnView should show images while loading, and be able to stop and move immediately to the next image if the user decides so.