I'm not sure why you would want your original background image. The one I made for you is about 17k as opposed to about 119k for the original. Unless, you can tell the very subtle difference in resolution. If that is the case, I can probably make a version at about 25k that has the same resolution as the original. But I can guarantee you that no one else would ever know the difference, and that 17k is better 25k for dial up and other slow connections. The k byte savings in either case is significant, but only matters on slower connections, like dial up, or even with broadband when there is any network slow down.
If positioning is the issue, that can be tweaked in the style section.
You can easily change the images used in the show, in this case substituting:
Code:
fadeimages[1]=["LunarRecords_8.gif", "", ""] //plain image syntax
for:
Code:
fadeimages[1]=["LunarRecords_6.gif", "", ""] //plain image syntax
Now, about the fade rate. I think the rate in my demo is optimal, but you can slow it down more. The spots where I modified U Fade are as follows:
Code:
function fadeshow(theimages, fadewidth, fadeheight, borderwidth, delay, pause, displayorder){
this.pausecheck=pause
this.mouseovercheck=0
this.delay=delay
this.degree=0 //initial opacity degree (0%)
this.curimag . . .
That line was:
this.degree=10 //initial opacity degree (10%)
and:
Code:
function fadepic(obj){
if (obj.degree<100){
obj.degree+=2
if (obj.tempobj.filte . . .
That line was:
obj.degree+=10
and:
Code:
fadeshow.prototype.resetit=function(){
this.degree=0
var crossobj=iebrowser? ie . . .
That line was:
this.degree=10
The two changes to 10 from 0 just set the images to start fading in from complete invisibility rather than 10% opacity. The change from 10 to 2 slows down the fade rate. To make it slower, 1 is the next option, but I think that is too slow. There is one other place you can edit, to slow things down by only a little. That's here:
Code:
fadeshow.prototype.rotateimage=function(){
if (this.pausecheck==1) //if pause onMouseover enabled, cache object
var cacheobj=this
if (this.mouseovercheck==1)
setTimeout(function(){cacheobj.rotateimage()}, 100)
else if (iebrowser&&dom||dom){
this.resetit()
var crossobj=this.tempobj=iebrowser? iebrowser[this.curcanvas] : document.getElementById(this.curcanvas)
crossobj.style.zIndex++
fadeclear[this.slideshowid]=setInterval("fadepic(fadearray["+this.slideshowid+"])",50)
this.curcanvas=(this.curca . . .
In this case, increasing the number 50 in the above will slow things. You shouldn't increase it by much though, because too much of an increase will make the transitions choppy. 60 or 70 are about as high as you should go.
One other issue that I'm not sure you are aware of, by removing (red):
Code:
new fadeshow(fadeimages, 435, 237, 0, 5000, 1, "R")
you will remove the random nature of the show, making it always start with the first image. As things are now, that would be this image:
Code:
fadeimages[0]=["Moon.Wav MusicMedia_3.gif", "", ""] //plain image syntax
Bookmarks