klaus2 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'...
What I can see as an option is: progressive loading/display (some people want early display for speed, some people want a one-time display for comparison purpose...)
Olivier PS: and I support the suggestion to show a 'progress bar'(and/or number) to show the status for caching images...
i can image that use case very well - at least for me it is a typical situation to "find" a next (fifth, sixth, ..) image by stepping forward widh pgdown ...
so it is not a bad idea do "cancel" a paint operation when not needed.
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. a loading time would be good too, after the progress bar is full.
"|||--------------"
"||||||||||||-----"
"|||||||||||||||||"
"Loaded in 0.8s"
Ad decus et ad libertatem nati sumus
Aut haec teneamus aut cum dignitate moriamur
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:)
Right: I think this the most important performance issue in XnView right now (and probably a 'stopper' for a lot of people). => XnView should show images while loading, and be able to stop and move immediately to the next image if the user decides so.
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... (it also has some negative impact on XnView's reputation)
Pierre: any update/opinion on what could be done to improve performance here?
if you'd check acdsee (at least 2.x version), you'd see, that when walking through images, if you press and hold page down, you see that you go through images blazing fast AND you even see a tiny bit of them appear on screen. if you try this in xnview it goes slooooooowwww
(feedback from a guest:)
full support!
For me it is a top issue to get rid of this negative comparison.
The good news is: it should be fixable by feasible means, using the proposal given (cancel paint if next image requested).
