Open Interface before loading Images

[Dstruct]

One thing I find very bad:

When XnView isn't opened, if you load very large images (by doubleclicking them in the Windows Explorer), the Interface gets opened too late IMO.

Wouldn't it be much better to have the interface opened first and then loading the image. This way I could see that XnView does something (progress/loading-bar).

At the moment it looks like nothing happens when opening large files (if xnview isn't opened already)


Here an example: http://www.outburst-audio.com/maik/artweaver-lzw.tif (6.2 MB)

-> close XnView
-> doubleclick the file to open it in XnView

=> XnView needs 5 seconds to show it and the interface itself

So in this example it would be much better to open the interface first and then begin with loading the image!

[pic_viewer]

2.5 seconds on my 3 GHz Dual 2 Core (E8400).

(Sorry, couldn't resist).

[Dstruct]

still too much. 2.5 seconds where no one knows what's happening in the background. other image viewers and graphic-programs don't behave this way.


btw: 5 seconds was taken on my intel e6700 dualcore (2,66 GHz)

[Dstruct]

besides this, i have another problem with this file. i can't get it to load in total commander's (7.03) lister. the file just shows up as binary. smaller images load fine in the lister. of course xnview is configured as image-viewer in total commander!

http://www.ghisler.ch/board/viewtopic.php?t=19075 (german)

[Dstruct]

more opinions on this problem (initial post)?


also when having thumbnail-cache enabled, if you click on a folder in the browser, XnView needs quite some time to open that folder. there it also would make much more sense to open the folder before loading the thumbnails!

at the moment all those actions always make me think that XnView hangs. would be nice to make it more responsive.

[xnview]

When XnView isn't opened, if you load very large images (by doubleclicking them in the Windows Explorer), the Interface gets opened too late IMO.

Wouldn't it be much better to have the interface opened first and then loading the image. This way I could see that XnView does something (progress/loading-bar).

Yes, right, i'll try to fix it

Besides this, why does XnView (1.93.6) need ~430 MB memory here to show this image?

12000x12000x3

[Dstruct]

Yes, right, i'll try to fix it

great, thanks!

[Dstruct]

Any news on this?

[JohnFredC]

Perhaps this fix would also address the incomplete painting of the XnView interface when opening a new browser tab?

On my system, the area beneath the main menu doesn't get painted until the tree and thumbs have completed display. When the current folder is a slow network share, this can take a long time (5 seconds or more)

XnView has behaved this way as long as I can remember. It looks unprofessional, to me. A subliminal thing, perhaps.



Best to paint the entire display either first (before validating the folder tree) or in a separate thread...