ok...solved the issue of timing. the system we use is placing br tags in spite of the fact that this was all coded in their html module. i got around it by eliminating all returns and spaces in the code. (the a tags had nothing to do with the timing issues...only the spaces and returns...just in case someone else runs into a similar issue)
i'm still having a strange issue with all four images loading initially on top of each other, and then moving into the slideshow. can you shed some light on why that might be? On Nov 13, 4:54 pm, "danny.copel...@gmail.com" <danny.copel...@gmail.com> wrote: > ### Insight: > > Cycle is trying to fade those break tags as well. It just finds all > direct children of "#homepage", in your case, and those are the <a> > tags and the <br> tags... > > On Nov 13, 5:52 pm, "danny.copel...@gmail.com" > > <danny.copel...@gmail.com> wrote: > > Oh, wait! No, what the actual problem is is that you have <br>s after > > each anchor...remove those and you should be golden. You can still > > play around with the delay option to get the timing right afterwards. > > > Also, those are HTML break tags, if yr ever going to use that to give > > content a line-break, pls use <br />, which is valid XHTML - the same > > as your DOCTYPE declares. > > > Good luck! > > > Dan
