any input would be appreciated on improving my short script used to show and then hide buttons after 5 seconds.
Thanks, Mike.

var buttons = [
"Btn1",
"Btn2",
"Btn3",
"Btn4",
"Btn5"
];

// SHOW BUTTONS
for (var i = 0; i < buttons.length; i++) {
CF.widget(buttons[i]).visible = true;
}

// HIDE AFTER 5 SECONDS
scheduleAfter(5000, function() {

for (var i = 0; i < buttons.length; i++) {
CF.widget(buttons[i]).visible = false;
}

});

I have something similar to remove a banner after a few seconds from the home page...

from the config file:

scheduleAfter(3000, function() {CF. widget("SPLASH").visible = false; } );

You could probably gain some efficiency by only querying the length of the array once and using the answer in both loops.

I only have a couple of things to note and these are a matter of preference.

I would use GUI.widget() vs CF.widget(). In your page script, create an array of the widgets vs just the tags of the widgets. Then in your scheduleAfter function just reference the widget entry in the array vs having to call CF.widget() a 2nd time.

There is a thread in this forum that discusses the difference in GUI.widget() vs CF.widget(). I prefer the former.

[Link: remotecentral.com]

[Link: remotecentral.com]

Thanks, after posting I already changed to GUI.Widget. I remembered that from other posts we have conversed on. LOL I shall play around more with the script above which is just my starting point. My goal is to have a popup with volume info displayed. IE. when I click on vol+ button, it will display on screen for a few seconds. Haven't decided if I just want to display a number or if I want to have some sort of graphic representing the volume.

Keep in mind that you will lose press and hold functionality on the Vol keys when you put script there. The only way to overcome this will be to create a 'onHold' function for your Vol keys. When you do this, you will likely find that your volume control is sluggish. If using a Marantz or Denon, you may also find that the toggle bit in the IR becomes an issue. Sony or Yamaha will likely have less of an issue with this.

yeppers have to do onHold any ways, vol is RS232

If your head unit a Denon or Marantz? If so, they likely send responses that include MVMAX after a volume change. My TCP/IP proxy ignores that value as I could care less. It is just noise.

If a Marantz, you should be able to Mute Toggle by sending the Extended Code over 232.

var RC5_IR_MUTE_TOGGLE_BY_ZONE = {'Z1':'RC516013','Z2':'RC51602908','Z3':'RC51609308'};

You can toggle mute for one of the 3 zones above by sending 'RC' + zone RC5 string.

For example:
var RS232CommandToSend = 'RC' + RC5_IR_MUTE_TOGGLE_BY_ZONE['Z1'] + '\r';

It be a Marantz, surprisingly Marantz does not have a toggle mute (least for my model, according to their documentation, never look further then that), so I already query the status and send the proper command, IE Mute ON or Mute OFF based off feedback. I will have to try to see if you are correct on automatically getting feedback back when sending a volume command. I would not be surprised if so, common on RS232 to get a response.

I presume you are using ProntoScript for all this and an extender.

Send this command 'RCRC5516013\r' via 232 and I bet you will find that your mute toggles. (This toggles zone 1).

'MVUP\r' will give you 2 strings of responses.
'MVXXX\r'
'MVMAXXXX\r'

The 'MVMAX' response was intended to let you know how much you could raise the volume but I found that it is not always correct.

Thanks, I don't remember what commands in the script I used for mute, set that up about a year ago and not home ATM. I think it was MUON\r and MUOFF\r. I figured there would be a toggle command out there just never investigated past there documentation for the unit I had. So far, my script has never failed for mute.

For the Marantz, they support extended IR commands (single shot only) via the 'RCXXXX' extension in the 232 or TCP/IP protocol.

For example, you can toggle Audyssey Dynamic Volume via IR but what I've found is that commands like this one and surround mode commands like 'MSMUSIC' on the first send only brings up the onscreen menu. You have to send 2 times to get the surround mode to actually change. Kind of annoying but I've gotten around it in most cases.

The one that I hate most is 'MSPURE DIRECT' which toggles the Pure Direct mode between either STEREO or DIRECT.

Definitely try out the Mute toggle I listed because it is a godsend. It just works. You send that and via 232 or TCP/IP you get feedback as to the mute status immediately without having to issue 'MU?'.

Thanks, I like my method only for I may be using more than one type of controller, IE. C4 or URC at the same time, so quiring the state and then send the command works better me. lol

I'm of the opinion that when you press mute, you already know the state and as such you want to change it. Yes, I used to query the state and change it but I found that I could use IR over TCP/IP with a simple RC5 command to toggle the mute state. Made things much easier.

Volume is still problematic as MVUP and MVDOWN are too slow in my opinion. You cannot do a full volume ramp in 30 seconds (the time limit the Pronto imposes on pressing and holding a button).

So, I created a volume ramp array in my TCP/IP module that uses 2DB increments <-40db and 1db increment above -40db up to -10db where .5db increments are used.

I query volume and determine what is the next setting based on direction (up or down). Based on the next setting, I set the volume for that value. It is a fairly smooth ramp and works nicely. You can change volume on the Marantz using IR commands to set 1 of 63 different levels. I played with that but determined there was not much benefit over what I currently use.

Thanks for the info, I never seemed to mind the ramp up/down speed from the pronto via RS232. On URC and C4 can be painfully very slow (let's not get me going on those issue, lol). I'm not a fan of using IR if RS232 is available. Yes, most reliable IR is, but I hate IR mice or blasters, more wires running, falling off and pain if you need to move a piece of equipment. But I do like your idea of ramping up based on level, I will have to play around with that.