Glad to help. It was helpful for me to visualize how the widget buttons are located by the ProntoScript and how much name/taging is needed.

If your ProntoScript is on the page with the widget - only need widget tag
If your ProntoScript is on a different page but within the same Device/Activity - widget and page tag (this is the case with the example for rotary function)
If you are on a different page and in a different Device/Activty - widget, page, and activity tag.

Try out the example for holding device variables that is useful for toggle power only devices. This is slightly more complicated but will help you understand better. Look for the string titled ProntoScript Devices Status Tracking for Beginners. I would put a link here but I could not figure out how.

If you want to wait I uploaded both config file examples in the Files section so they should be available there soon. You could then open the files to follow along with the narration.

I have seen somebody using a video server to display the satelite's menu on the panel. My AMX panel does that, but it is an easier thing to do. It would be nice to use the rotary function to make this happen.
I suppose one could preview all channels etc on the panel and navigate into all menus.
A plain vanilla "Watch" Button could turn the TV, Amp,etc on.

Has anybody done this?

Great stuff. Read a different post last night and had zero luck. Read yours and was saved another headache as you pointed me to my obvioulsly overlucked inferior firmware version >.< I'm also a "hobbyist" and while I'm in the middle of a CS degree, after years of playing around led me to go back to school for another degree, I couldn't be confident in my scripts and kept trouble shooting the code instead of looking at the bigger picture. Thanks again!

I thought I'd share my simple code for changing the volume with the wheel, based on the above examples.

// ROTARY WHEEL TV VOLUME ADJUST
onRotary = function(clicks)
{

if (clicks > 1)
{CF.widget("PS_VOLUME_UP").executeActions();}
if (clicks < -1)
{CF.widget("PS_VOLUME_DOWN").executeActions();}

};

I still don't get this!

I'm running firmware 4.0.17

I'm using ProntoEdit Professional 2.0.35.0 (latest version)

I copied example 2 in the original post into the Activity Properties / Advanced page of my "watch Sky" activity. (Sky is satellite PVR). I gave it a prontoscript name of "test".

I created a hidden page in the "Sky" activity called "rotarypage"

I created 6 buttons in the "rotarypage" page, tagging them in "advanced" with the prontoscript names as shown in the example.

I added the IR actions to each of the 6 buttons.

I saved the project, then downloaded it. When I go into the activity, the wheel clicks when rotated, but I don't get any IR activity.

Any ideas what I'm doing wrong?

Did you put ProntoScript names on all buttons, pages and activities in use? Do these names match the names in your script?

I created a config file that is now posted in the files section. Download this and it will give you a working example to look at.

Herb

After posting, I stopped to eat, then sat down to watch some TV. Tried the wheel, and it worked!

Seems that I'd done it right, but got confused because the "IR activity indicator" (bit that swirls round at the top left of the screen) doesn't show anything when the wheel is moved. Any reason why this should be the case?

While I was playing around in ProntoEdit, trying to get it to work, I ended up with a cut down script that contained just a "<-1" and a ">1" command for rewind and fast forward, so 2 clicks (or more) transmits the command.

If I rotate the wheel slowly, nothing happens - I have to rotate the wheel quite fast.

Is there any way to control the speed at which the clicks are read? That is, how do I ensure that 3 clicks are read as one command of 3 clicks, rather than 3 separate commands of one click each?

Also, if I want to execute a command when the wheel is moved just one click, I use "== 1" as the operator. If I want any input of one or more clicks to send just one press, do I use ">= 1"?

If you have executed whatever you need in onRotary() the goal of the remote is to call this function each 100-150ms and provide the number of clicks encountered in that time period. Once you stop rotating the wheel, you will get an update where clicks is 0.

You can write your own algorithm in to measure 3 clicks in any period of time if you see fit but just know that the remote will notify you of clicks typcially in this timeframe. :)

Great post Herb!

Really helps to put some function on that wheel...

Thanks!

the problem was the missing scriptname of my Page3

thanks

now it works fine

+1

Thanks to this post plus the .xcf example in the files section, Even I is now capable of putting the rotary wheel in to use(crude but still in use).


//Mats

Hi
I have finaly got the rotarywheel working :-)
I'm using it för controlling volume on my HK AVR247.
It works but i would like to have it a bit smoother.
As for now, if i turn the wheel slow every klick + or - one vol level.
But if i turn the wheel faster a lot of klicks does not registrate.
I tried to have another copy of my vol in my database with different duration (0.8)but then the vol jumped a bit uncontroled.
I would like the wheel work as nice as if i turn the manual volumewheel at the HK AVR 247.
Any suggestions to make it work that way would be nice!
I hope my bad english is understandable.

/N

I have seen several algorithms to smooth out the wheel. See the dev guide or also search this forum for +smooth +scroll (or something like that) for an algorithm that uses logarithmic functions for smoother scroll.

Personally I found the jog wheel a little too easy to touch when reaching for something else (volume control, beer, etc.) and found myself jogging inadvertently. So I was doing annoying things like fast forwarding or changing channels when I didn't want to (causing wife to cry "what are you doing? I was watching that"). I think these types of critically controlled actions are best left to hard buttons.

What I ended up using it for is dimming or brightening the primary lights based on one, two, or three clicks. I put the script in each device so no matter what I am doing I always have quick access to light control. If I hit the jog wheel reaching for something else no big deal.

Herb