In absence of actually fixing the problem, some post-facto snapping would be necessary for this to be robust.

However I will be taking this demo as a starting point for the project I am working on and will make it more robust. Your comment will help me make it more so. Thanks!

David

So the line would be :

new Effect.MoveBy(’BigBox’, 0, -872 , {duration: 0.4, transition: Effect.Transitions.sinoidal, queue: ‘end’});

Hope that helps. Thanks again Dan for the comment…I probably wouldn’t have noticed this otherwise.

David

Check out the code on the robust demo and see if that helps.

Feel free to email me if you are still having trouble.

David

var locked=”false”;

function unlock() {
locked=”false”;
}

function lock() {
locked=”true”;
}

function isLocked() {
if (locked==”true”) {
return true;
} else {
return false;
}
}

function MoveLeft()
{
if (!isLocked()) {
lock();
new Effect.MoveBy(’BigBox’, 0, 872 ,
{
duration: 0.4,
transition: Effect.Transitions.sinoidal
});

setTimeout(”unlock()”, 1500);
}
}

Basically, it will take 1.5 seconds after the moving effect is over for the function to be unlocked - hence the user won’t be able to rapidly press the link.

queue: ‘end’

Thanks,
Jeevanbabuks.