Just to let everybody know that this feature will be part of jQuery Tools 1.1. It will be implemented as scrollable *plugin*. The main scrollable.js is totally ignorant of this new plugin making it a clean separate extension to the main functionality.

Currenlty I’m on a lengthy vacation and these things will be published after about two months.

function scrollTo(position) {
var api = $(“div.scrollable”).scrollable();
api.seekTo(position);
api.reload();
}

now, if you make a call, for example, scrollTo(3) – something funny happens – it scrolls somewhere but not to the 4th item on the list.

{foreach item=data from=$productdata}

<!—->
{$data.articlecode} {$data.articlename}
Colour range 1 190*145 mm

{/foreach}

and then i got the code to initialize it :

$(function() {

$(“div.scrollable”).scrollable(
{

interval: 0,

loop: false,

speed: 1000,

size:3
}
);
});

now yours is with a ul element etc…

@Rbs – can you provide more details? I’ll look into it though

@Marvin – thanx. the jw player is loaded into a lightbox with an iframe,using colorbox. So, once the lightbox goes away, the iframe does too. I guess because the iframe is a separate page, it’s properly unloaded and stops playing. Now, if the jw player were loaded as via an inline div, the movie would still be in the same page and you’d need to somehow remove it from the DOM to unload it. I have no testing to back up my theory but that’s how I figure it works.

@domi – you shouldn’t need to change a thing. I broke backward functionality by changing loop:true to a circular loop by default. I thought about adding another config item, something like “loopMethod = bounce/circular” but decided to leave that to the original author to decide.

I’m using the old version now, but what must i change in my code to get one as on your site ?

Tnx

Great idea to add this functionality. I noticed that the carousel on Ruckus Wireless is acting a bit odd if you click on one direction 5 or more times, it will break the carousel behavior and perform a “scroll really fast” to the final page.

I’m not sure if it’s the timer script triggering an auto focus causing the fast scroll back effect. If this not the case then, perhaps we need a queue system for the consecutive click actions as 5 clicks is JUST 1 greater than the total page count and that causes undesirable behavior in the loop tracking code… or it could be a coincidence.

Anyways, it’s a great idea and I would love to see this feature get polished.