After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 551210 - slideshow on ltsp client - prefetch image
slideshow on ltsp client - prefetch image
Status: RESOLVED DUPLICATE of bug 501512
Product: gthumb
Classification: Other
Component: general
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2008-09-07 11:19 UTC by stephan
Modified: 2008-09-11 12:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description stephan 2008-09-07 11:19:54 UTC
I'm using ltsp to display the slideshow on a client. that means the images are transferred via a (not so fast) lan connection. This results in a pause between pictures where nothing is displayed - the screen goes black - when using the fading effect. When not using the fading effect i can watch how the image data appear piece by piece. 

Woudn't it be a good idea to display the previous picture until the data of the next picture are complete. I suspect this should only be a minor change to the code?

thanks,
stephan
Comment 1 Michael Chudobiak 2008-09-07 13:12:42 UTC
Stephan,

the fading code is being rewritten in bug 501512. I don't know if the new code will be better or worse for you. You can add your comments there for the coder.

- Mike
Comment 2 dynamotwain 2008-09-07 18:59:55 UTC
Stephan,

Before, this wasn't possible because we could only have one image loaded at a time, thus requiring the next image to be loaded during the middle of the fade-out/fade-in sequence.

With my changes, any sort of transition effect don't begin until the next image is completely loaded, so this issue will go away once all of the other issues are resolved and it makes it into a new stable release.
Comment 3 stephan 2008-09-07 19:21:33 UTC
brilliant - this bug will be obsolete then.

regards,
stephan
Comment 4 Michael Chudobiak 2008-09-11 12:43:59 UTC

*** This bug has been marked as a duplicate of 501512 ***