I already have my "mute" button on my remote set to mute. I'd now like to be able to set it so that if I press the "mute" button 3 times very quickly, it will execute a batch program.
Basically what I am trying to do is reboot the machine if the mute button is pressed 3 times very quickly. I already have a small batch program that will shutdown my open programs and then reboot the machine. I want to be able to trigger this program with pressing the mute button 3 times, but I already have the mute button set to another command (mute).
Is this possible to set up?
Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
use remote button squence to trigger event?
-
specter333
- Experienced User
- Posts: 95
- Joined: Thu Dec 27, 2007 12:26 am
Re: use remote button squence to trigger event?
It's probably possible but tricky since your already using the mute key.
Off the top of my head, I'd let it go ahead and mute the system on the first press but also enable a macro.
That macro would disable itself if another mute command is not received in say 1 second.
If the second mute is received then it enables a third macro that would also disable itself if the mute command isn't received and if it is it would execute the reboot program.
I'll try to make that a little clearer.
First macro,
Receives mute
Mutes system
Enables second macro
Pauses or ignore events to keep a loop from starting
Second macro,
Receives second mute
Enables third macro
Disables itself
Third macro,
Receives third mute command
Starts reboot program
Disables itself
That's what I would do, maybe some of the more experienced guys can come up with a better way.
You could also try the jump if long press action. Maybe you could use a long mute press instead of three presses.
Good Luck
Rich
Off the top of my head, I'd let it go ahead and mute the system on the first press but also enable a macro.
That macro would disable itself if another mute command is not received in say 1 second.
If the second mute is received then it enables a third macro that would also disable itself if the mute command isn't received and if it is it would execute the reboot program.
I'll try to make that a little clearer.
First macro,
Receives mute
Mutes system
Enables second macro
Pauses or ignore events to keep a loop from starting
Second macro,
Receives second mute
Enables third macro
Disables itself
Third macro,
Receives third mute command
Starts reboot program
Disables itself
That's what I would do, maybe some of the more experienced guys can come up with a better way.
You could also try the jump if long press action. Maybe you could use a long mute press instead of three presses.
Good Luck
Rich
Re: use remote button squence to trigger event?
What about long button press?
pr0n!!!
pr0n!!!
-
jsonnabend
- Experienced User
- Posts: 127
- Joined: Wed Apr 23, 2008 7:35 pm
Re: use remote button squence to trigger event?
I have something similar in my setup. Maybe it will help.
I have a key that enters "macro" mode (it's the star key, but could be any key). In that mode, the system waits for up to three numeric key inputs, or one or two keys plus an "enter" key, or one or two keys plus a time out. It then fires an event based on the input number.
The way it works is that hitting the star key enables exclusively a node that processes the remote inputs (keeping them away from normal system control). At start of "macro" mode, a timer is set. If a key isn't received in that time, the node is disabled and the usual node re-enabled, ending "macro" mode.
If a key is received before the time out, the timer is reset, waiting for another key. When all three keys are received, or one or two plus "enter", or one or two plus a time out, the number-based event is fired.
This setup could easily be adapted for multiple key presses of the same key, I think.
I didn't set this up as a plugin, so I'm not sure how best to share my setup. If anyone has any ideas, I'm all ears.
- Jeff
I have a key that enters "macro" mode (it's the star key, but could be any key). In that mode, the system waits for up to three numeric key inputs, or one or two keys plus an "enter" key, or one or two keys plus a time out. It then fires an event based on the input number.
The way it works is that hitting the star key enables exclusively a node that processes the remote inputs (keeping them away from normal system control). At start of "macro" mode, a timer is set. If a key isn't received in that time, the node is disabled and the usual node re-enabled, ending "macro" mode.
If a key is received before the time out, the timer is reset, waiting for another key. When all three keys are received, or one or two plus "enter", or one or two plus a time out, the number-based event is fired.
This setup could easily be adapted for multiple key presses of the same key, I think.
I didn't set this up as a plugin, so I'm not sure how best to share my setup. If anyone has any ideas, I'm all ears.
- Jeff