Hi Jason,

It looks like you just want to a different action for each direction, but do it more times when the wheel is moving faster?

In this case don't worry about negative clicks (my multBy) just work out the direction and do the action clicks times.

Your code wasn't using "clicks" at all, so you may even find this will work without the acceleration. - ie remove the if and else clauses:

onRotary = function(clicks)
{
    var act = (clicks > 0) ? "PS_CURSOR_DOWN" : "PS_CURSOR_UP";
    clicks = Math.abs(clicks);

    if (clicks >= 6)         clicks *= 3;
    else if (clicks >= 3)    clicks *= 2;
    
    for (var i = 0; i < clicks; i++ ) 
    {
        GUI.widget(act).executeActions();
    }    
}

How does that work?
Brett

I want to thank those who have posted for the help. I couldn't get the remote to do what I wanted and I believe that it is a function of what I'm trying to get it to do. When I'm using the iPod or internet radio (Denon 4308), I would like to scroll through the music lists faster. Based on all the code I have been playing around with, I can't do it. I think the issue is with the receiver and not the remote. There isn't any code for the remote that will make the receiver scroll faster through the lists. No matter how much I turn the rotary wheel the receiver will go up or down the music list one line at a time. Thanks again.

I have successfully used the acceleration code provided in the Developers Guide, but I've noticed a small issue that doesn't seem to be correctable by altering the Prontoscript code.

The curious behavior occurs after scrolling for several clicks in a particular direction (+ or -), followed by a complete stop & pause, followed by an attempt to scroll in the opposite direction. Quite often when I do this, the first "click" value returned by the operating system after initiating scrolling in the opposite direction will have a value corresponding to the original direction of scrolling instead of the new/opposite direction of scrolling.

Has anyone else noticed this? The only way I've found to make this go away is to require at least 2 clicks before responding to the input, but doing this really slows down the interface. I'm starting to wonder if this might be a problem with the firmware?

I'll be interested in finding out if anyone else has noticed this problem.

Have not noticed this with the new firmware. Interesting though.

I noticed that if i use the snippet from brettd, it works but if i change the time on the ir signal to "minimal" it doesn't work anymore with the scroll wheel. It does send information to my rfx, but no response. If i push the normal buttons it still works..

update: confirmed, values of 0.1 with scroll wheel does not work. Using regular buttons via the rfx9400 works normally.

This a bug perhaps then? or maybe it does not allow 0.1 value's? Dont know any other options on how to speed up zapping.