I am using unclemiltie's new extender for the Insignia remote. I have successfully converted ny Atlas based extender setup to this new remote and extender. Thanks for the great work unclemiltie!
I have started exploring using DKP/LKP and I am having some problems, but they are likely due to the fact that I have never used these functions in previous extenders as ooposed to problems with the extender and thus why I am posting in a new thread as opposed to unclemiltie's extender thread.
DKP/LKP appear to be device and key specific. I guess my question is if I setup particular device/key LKP and attempt to execute that device/key in a macro ... should it pass the macro key press duration into the commands being executed in the macro so that they take different actions on executed DKP/LKP defined device/keys based upon the duration of the original keypress?
The reason I ask is because it appears to always be executing the "Long Press" actions in the LKP definition regardless of the LKP Duration setting or how long the original macro key is pressed.
Any help would be appreciated.
Thanks, Greg
Extender DKP/LKP
Moderator: Moderators
I'm using unclemiltie's RCRP05B extender rather than the Insignia one. But since the latter was derived from the former, one would assume that they should both behave similarly.
That said, I do indeed have instances where I've defined an LKP on a particular device/button, then created a global macro that switches to that device and triggers that button as the last steps of the macro. And in my case, the duration of the macro key press is carried over to the execution of that final LKP.
So for instance, I have an LKP on dev6/Phantom3 where a short press shuts off the current device (Dev_Cancel, XShift-Power) and a long press shuts off all devices. I then have a macro on the Power button that executes Dev_dev6,Phantom3. And short/long presses of Power perform exactly as expected.
That said, I do indeed have instances where I've defined an LKP on a particular device/button, then created a global macro that switches to that device and triggers that button as the last steps of the macro. And in my case, the duration of the macro key press is carried over to the execution of that final LKP.
So for instance, I have an LKP on dev6/Phantom3 where a short press shuts off the current device (Dev_Cancel, XShift-Power) and a long press shuts off all devices. I then have a macro on the Power button that executes Dev_dev6,Phantom3. And short/long presses of Power perform exactly as expected.
-
vickyg2003
- Site Admin
- Posts: 7104
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
Greg, I've got some documentation here
http://getzweb.net/jp1/howto/vicky/fldensetup.htm
that might help you get a handle on how to use an LKP.
http://getzweb.net/jp1/howto/vicky/fldensetup.htm
that might help you get a handle on how to use an LKP.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
It is as intended. Call to the LKP placed inside a macro is a short press. So it must always be the last command.TheGMan wrote:I got the LKP to work if the macro calls the defined LKP device/key as the last step in the macro. Not sure if that is as intended.
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride