Crash on scroll
Posted: Sun Mar 06, 2011 2:13 am
Hello,
I lost overview a little bit, so sorry if this is still on the list.
In the left dir tree pane, scrolling the cursor over the dirs by the navigation keys is a stumbling and delayed experience. I remember I had this long ago and then must have given up. It seems XnView reads in the content of every dir to display the thumbnails first, and depending on the number of files (photos) found it then needs some time to move on. The user experience here is that of a slow and crawling software. It should be easy to delay that read-in (or display) a bit so that a held down navigation key lets the cursor just move up/down in a constant speed.
Now the main reason I write this: I tried XnViewTweakUi yesterday. Browser active. I disabled the option 'Use delayed preview' (was set to 200 ms) to see if that speeds up the cursor scrolling over the dir tree. By helding down the cursor keys and changing directions 2 or 3 times XnView crashed. Not with 100 or 200 ms delay, but every time this option is off (is that 0 ms then?).
2 things to fix, IMHO.
I lost overview a little bit, so sorry if this is still on the list.
In the left dir tree pane, scrolling the cursor over the dirs by the navigation keys is a stumbling and delayed experience. I remember I had this long ago and then must have given up. It seems XnView reads in the content of every dir to display the thumbnails first, and depending on the number of files (photos) found it then needs some time to move on. The user experience here is that of a slow and crawling software. It should be easy to delay that read-in (or display) a bit so that a held down navigation key lets the cursor just move up/down in a constant speed.
Now the main reason I write this: I tried XnViewTweakUi yesterday. Browser active. I disabled the option 'Use delayed preview' (was set to 200 ms) to see if that speeds up the cursor scrolling over the dir tree. By helding down the cursor keys and changing directions 2 or 3 times XnView crashed. Not with 100 or 200 ms delay, but every time this option is off (is that 0 ms then?).
2 things to fix, IMHO.