That wasn't made an option because it relies upon two factors which if they get out of whack can easily result in choppy fades. If you consider the delay in relation to how long it takes an image to fade fully in, that makes three factors and for the possibility that an image won't have time to fade fully in before it starts to change into the next image.
That said, feel free to play with it. The two factors I mentioned may be found in the swissarmy.js file itself by searching for:
fadepic
which only appears twice in that file. The first time:
Code:
inter_slide.prototype.fadepic=function(){
if (this.fade&&this.degree<100){
this.faded=0
this.degree+=10
if (this.tempobj.filters&&this.tempobj.filters[0]){
if (typeof this.tempobj.fil . . .
Notice the red 10, it is the opacity increment for each iteration of the repeating fade in cycle. If it is reduced, it will make the fade take longer. It must be able to divide into 100 evenly. Using values other than 20, 10, 5, or 2 will probably make for trouble.
The other factor is near the second instance of fadepic:
Code:
this.fadeclear=setInterval(function(){fadeobj.fadepic()},50)
Notice the red 50, it sets how often (in milliseconds) each iteration of the fade in cycle repeats. If it is increased, it will slow things down. 20 (which would be faster) is thought to be a minimum value, at 70 or more (pretty slow), the effect will probably start to get choppy.
So by adjusting these two numbers you can have some control over the fade in rate. Just be aware, as I already mentioned, that if you slow the rate of fade in to a point where it takes longer than the delay, no image will ever fade fully in. And of course beware of making the transition choppy if these two values get too far out of whack. The exact numbers where this will happen vary in relation to each other and to the size (both in dimensions and bytes) of your images. Different browsers and systems will also vary in this.
Bookmarks