I have a widget that contains an action list of 1 Database IR code. If I press and hold the widget button down, the IR code is repeated as it should. If I refrence this widget with a script using executeActions() then the code does not repeat. The onlyway I can get it to repeat is onHold() and onHoldinterval() set to 1 millisecond. This does repeat the code while holding the button down but not as good as holding the button down that holds the IR code.

Can someone please confirm whether executeActions() should repeat the code as the original widget?

Looks like you may already have your answer.

If you are familiar with IR code formats, you could, in theory, separate the non-repeat and repeating parts (see Barry Gordon's document in the Classic Pronto Files Section on Pronto Hex IR Format). You would then have a non-repeating and repeating button and based on what you needed, you'd issue executeActions() on one of these buttons. I've been working with winnipeg300 on something like this using the jog wheel. Have not had much luck with this approach as of yet.

However, there's still hope. (Thanks Peter). Try adjusting the duration of the IR from something other than default to something longer. If this works then please post back.

Using ExecuteActions on a single action is like the behaviour you get when an action is in a macro. It only gets executed for a fixed (short) duration. There are no parameters on ExecuteActions to specify how long to send the codes.

Using OnHold with OnHoldInterval is equivalent to pushing teh button several times. It is not like a continuous push.

I think Lyndel's suggestion of adjusting the duration is most likely to get what you want. Just adjust the code's duration and use a single ExecuteActions.

Well I've tried adjusting the duration, this seems to just repeat the single press code for the duration specified. If I keep the button pressed it does not carry on repeating the code. I have tried a learned code and also a database code. executeActions() will not repeat the code while the button is pressed at all.

Using onHold() and onHoldInterval () is working ok. I was just curious as to whether executeActions() should act the same as pressing the original widget button. I can now see it doesn't.

Rich

As I said in my previous post, there is no parameter for ExecuteActions to specify how long to transmit the code. Holding down the button that triggers ExecuteActions has (and cannot have) any bearing on how long the code is transmitted.

I'm surprised adjusting duration did not do anything. If you set it to something like 2 seconds, it should behave the same way as pressing a normal button with a single action for 2 seconds.

Your original post is confusing as you use the word widget instead of button. Widget is only a term use din ProntoScript. So, just to be clear:

You have a normal button with an IR Code, and NO ProntoScript. If you press and hold, it transmits continuously. Now if you increase the Duration on the IR Code to something like 2 seconds, and press the button briefly, you should see it transmit for two seconds.

If that works, you should find that if you use ProntoScript to ExecuteActions on that button, you should have the same result.

Alos, you have not said why you want to do this in the first place. There may be another way of getting what you want.

What Peter says is correct. I don't believe you can get the repeat par to xmit unless you useonHold() and call executeActions() from there.

I will pass a link to this post along to my contacts in Belgium for confirmation of the behavior.

Lyndel

Hi All,

This is indeed a bug which we are still investigating on how to solve it.
As a workaround you could try the following although it will not work with every IR code.

Buttonscript:

button1.executeActions();
onHold = function()
{
button2.executeActions();
}
onHoldInterval = 1;

//where button1 is the original IR code but with a small last off time
//and button2 is the IR code with only the repeated part and also the same small last
//off time

Kind regards,
The Prontoteam

This is something I will look into.. Unfortunately it cant be done with a database code. Perhaps we could have executePress() and executeHold() to enable us to specify whether we need the one time code or the repeated code to be transmitted

This approach has been discussed privately via email by myself and by Peter to the ProntoTeam.

I initially forwarded this issue along to Belgium for direct comment. Rest assured they are looking to find a solution.

I know this thread over a year old, but I am having the same issue described here, and was wondering if anyone has found a real solution yet?

As the original poster said, calling executeActions() within the onHold function works, just with nowhere near the responsiveness you get by using a normal action list. I tried increasing the duration of IR code, which it helps slightly, but still not as well as the normal action list.

I have not been able to try the ProntoTeam suggestion using a second version of the code that contains only the repeating portion, because I have no idea how to figure what part of the code that is.

Please post the IR code data and I will break it apart if I can. There is no other solution available at this time.

I am sure Lyndel will be able to break it apart, but if he gets stumped I would be willing to take a look at it.

Here are the codes.  They are both panasonic devices, unfortunately I do not have the exact model numbers at hand, but I can get that info shortly if it is needed.  I very much appreciate the assistance.

Audio1 - Volume Up

0000 0071 0000 0032 007F 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0AA5

Audio1 - Volume Down

0000 0071 0000 0032 007F 003F 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0AA5

Audio2 - Volume Up

0000 0071 0000 0032 007F 0040 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0AA9

Audio2 - Volume Down

0000 0071 0000 0032 007F 0040 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0010 0030 0010 0AB1

Thank you very much for the help!

PS: For the record, (you can probably guess), specifically what I am trying to accomplish is the ability to switch audio out, without the redundancy of multiple Activities (which would be identical except the Volume/Mute hardbuttons).  My current script solution tests well except for the sluggish responsiveness, which isn't acceptable to me.  I hope that isolating the repeating portion of the code improves it to be at least good enough, and hopefully identical to the snappy response of using an normal Action List.  My 'onHold' function is as tight as it possibly can be, literally one line: "activeAudioOut.executeActions()"

You may not have much luck with these codes as they don't have a large one-shot and small repeat but instead no one-shot and large repeat. Try changing the first 4 sets of numbers to:

0000 0071 0032 0000

Which effectively makes the repeating part the one-shot with no repeats. Note: You will want to use your original IR codes for regular non-scripted buttons as these codes won't repeat if used there. (See Barry's Pronto Hex IR Format doc in Classic Pronto Files section for better understanding of what I did).

Not sure this will make much difference but it might.

No dice, but thank you very much for taking the time to help, and I appreciate the pointer to Barry's document -- I much prefer to try and understand this stuff myself rather than simply following suggestions and not really knowing what is being done.

I think I am going to go ahead with the slowness of the volume up/down and see if it flies. If after a few weeks it's just not acceptable, I suppose there's no alternative to duplicating the entire activity in order to achieve what is needed.

Thanks again - bdc