What do you mean press? Are you using an iPad or other device with a touchscreen? If you mean click though, that means that either the Ufade images have no links, or that something about the layout is covering them in some unseen way. To have a link for an image in Ufade, you need to have the second field in the image array entry filled in, for example in this excerpt from my working demo:
Code:
var mygallery=new fadeSlideShow({
wrapperid: "fadeshow1", //ID of blank DIV on page to house Slideshow
dimensions: [250, 180], //width/height of gallery in pixels. Should reflect dimensions of largest image
imagearray: [
["http://i26.tinypic.com/11l7ls0.jpg", "", "", "Nothing beats relaxing next to the pool when the weather is hot."],
["http://i29.tinypic.com/xp3hns.jpg", "../content/ohoopee1.jpg", "", "Some day I'd like to explore these caves!"],
["http://i30.tinypic.com/531q3n.jpg", "", "", '<a href="http://www.google.com/" target="_new">Google<\/a>', ' '],
["http://i31.tinypic.com/119w28m.jpg", "", "", "What a beautiful scene with everything changing colors."] //<--no trailing comma after very last image element!
],
displaymode: {type:'auto', pause:2500, cycles:0, wraparound:false},
persist: false, //remember last viewed slide and recall within same session?
fadeduration: 500, //transition duration (milliseconds)
descreveal: "ondemand",
togglerid: "",
oninit: fadeSlideShow.myoninit
});
only the highlighted imagearray line has a link. So only the i29.tinypic.com/xp3hns.jpg (it's the image of a cave) would be clickable. And in the examples from your post, this one for instance:
Code:
imagearray: [
["/AppImages/Customers/Nolio.jpg"],
["/AppImages/Customers/HP.jpg"],
["/AppImages/Customers/Gilevents.jpg"]//<--no trailing comma after very last image element!
],
None are linked, so there will be no ColorBox and none of the images can be clicked. With ColorBox and this setup, you can link to a page on the same domain (it will be fetched via AJAX, which has some limitations), or to an image anywhere on the net or in the local testing environment.
Usually you would want larger or different images. Just to test though, you could use the same images:
Code:
imagearray: [
["/AppImages/Customers/Nolio.jpg", "/AppImages/Customers/Nolio.jpg"],
["/AppImages/Customers/HP.jpg", "/AppImages/Customers/HP.jpg"],
["/AppImages/Customers/Gilevents.jpg", "/AppImages/Customers/Gilevents.jpg"]//<--no trailing comma after very last image element!
],
I tested it here before posting it and it works fine. Unfortunately though, I don't have a testing environment for asp. So if the above is not the solution, it would be hard to say. But asp is essentially like any server side code. What counts in a case like this is what's in the served source code of the page. Look at the page in the browser. Use its 'view source'. If the source code isn't as I have laid out, then it needs to be changed on that page or on some page used by the server to make that page.
That's not the only thing that can go awry using server side code to assemble a page. Once you start using includes and similar server side files and/or other server side techniques, it can be easy to inadvertently mess up a path or paths for the actual page.
In this case (because I have no asp testing environment), the only way I could tell any of that is if I could see the page live. If you have Firefox, I could probably guide you through the steps needed to check these things on your own.
Bookmarks