Enable or disable blinking spots when waiting or between pictures

[GoogleCodeExporter]

Hello, is there any possibility to disable the HBO-like waiting screen ?
Due to a disease it generates troubles in my eyes when I browse between 
pictures.

Thanks,
David

Original issue reported on code.google.com by vddoor...@gmail.com on 14 Jun 2013 at 1:26

Attachments:

• [Capture d’écran 2013-06-14 à 15.21.11.png](https://storage.googleapis.com/google-code-attachments/xee/issue-347/comment-0/Capture d’écran 2013-06-14 à 15.21.11.png)

[GoogleCodeExporter]

I am planning on adding some more options for loading animations later. For 
now, try switching visual style, as the other ones are darker and might be less 
annoying.

Original comment by paracel...@gmail.com on 14 Jun 2013 at 1:35

[GoogleCodeExporter]

Issue 348 has been merged into this issue.

Original comment by paracel...@gmail.com on 16 Jun 2013 at 1:20

[GoogleCodeExporter]

Love Xee, long time favourite. The lost signal pattern between images is very 
distracting - please make an option that fades between images or just overlays 
the next image instead of displaying this. It is too jarring and makes me go 
back to the older versions of Xee.

Original comment by c.cl...@gmail.com on 20 Jun 2013 at 6:01

[GoogleCodeExporter]

Issue 353 has been merged into this issue.

Original comment by paracel...@gmail.com on 7 Jul 2013 at 8:45

[GoogleCodeExporter]

I understand the benefits of having a 'loading in progress' image -- but agree 
with others, that i'd like options to tweak it.  A few additional 
ideas/thoughts though:

- You seem to show the 'static' AFTER you've parsed the new file -- as the 
static shows the new picture's dimensions, then static, then the image.  So 
give you know the picture dimensions, i'd like the option for a 
white/grey/black placeholder instead.

- Alternatively, if some of the overhead is parsing the new file -- what about 
a visual effect on the CURRENT image to show that you're loading the new one.   
e.g. do a vignette (e.g. dark barrel effect around the edges) to show that this 
image is about to disappear ... but still allowing us to look at something 
while the new image is loading.  A simple 'smokey semi-opaque overlay with a 
spinner' would also work -- but i personally recommend a photo-effect like this 
that keeps the current image still visible.

In addition to this, I would like to see some pre-buffering done to try to 
minimise it. It's possible this is happening, but from my test with large files 
it didn't appear to be:

- buffer next 2-3 images
- buffer previous 1 image 
- buffer the next 'random' image

This will minimise the number of times that people see the 'loading effect' in 
any situation.

Prebuffering possibly needs to be an setting toggle; Or to minimise memory 
footprint -- you could always store a low-resolution prebuffered preview, and 
then load the high-res over the top of it when they go next image.

Awesome to Xee release a new version! And the process-separation will hopefully 
stop the random crashes. Thanks for a great viewer.

Original comment by mcac...@gmail.com on 9 Jul 2013 at 4:36

[GoogleCodeExporter]

Prebuffering is happening. The next image in the direction you browsed last is 
pre-buffered, and the previous image is also buffered.

Also, loading effects using the last image is not really possible, as it needs 
to work when swipe browsing.

Original comment by paracel...@gmail.com on 9 Jul 2013 at 8:35

[GoogleCodeExporter]

There are a few options now for loading animation. Might add more later if I 
get ideas.

Original comment by paracel...@gmail.com on 17 Jul 2013 at 12:38

• Changed state: Fixed

[GoogleCodeExporter]

So has this been fixed?  Is it now like it used to be, where when you moved 
from image to image it would just show one after another and not do any 
annoying things between the images?  My "trial" expired even though I 
uninstalled it with about 10 days to go to go back to the old version, so I was 
unable to reinstall and test it out a week or so ago.

Original comment by j...@fiorelli.us on 17 Jul 2013 at 12:44

[GoogleCodeExporter]

There will always be some loading animation, because it is not possible to do 
partial loading with the modern OS X APIs.

Also, you'll have to wait for 3.1 to actually be released to test it.

Original comment by paracel...@gmail.com on 17 Jul 2013 at 1:00

[GoogleCodeExporter]

Issue 362 has been merged into this issue.

Original comment by paracel...@gmail.com on 8 Aug 2013 at 6:06