unclemiltie wrote:
can you describe this more? jeff is seeing a weird problem with this xshift version of the extender as well, it looks like the keys that I moved around are "bouncing" somehow and he's seeing them fire more than once and not seeing it on the keys that didn't move. I'm still chasing it, but this one really has me scratching my head.
My issue, with shift and xshift, is completely resolved after I cleaned up my keymoves. I had duplicate assignments for some key presses, i.e. TV:power was defined in the upgrade as well as in a macro AND as a keymove. This was an artifact of using an ancient upgrade for mits tv's, that had double assignments to some keys.
mattg568 wrote:I deleted the built in upgrades before merging the IR file with the extender.
I think it has to do with the number of times you press the shift key.
Aha! I think you may have got it!
as you may have noticed, the change to make Xshift $82 may be the issue here. Shift is adding $80 to the previous key in all of the remotes and the extender. So Shift-Shift is $82, or the value for Xshift in the extender.
I've noticed something... When I install the extender, Shift keycode is 2 and Xshift keycode is 130. But when I download from the remote, Xshift keycode changes to 2.
can you send me your IR file? (PM me and I'll send you my direct email) I have to see that. There is NOTHING in the extender that rewrites data back into the extender code where the Xshift key is defined.
Weird. I've tried to duplicate the effect, but now it stays normal. What I did was delete IR and RM including the RDFs and images and create a new IR file.
you very well may have had the wrong RDF that was pointing to a different spot.
The way that this works is that the location specified in the RDF is the location of a hard-coded compare instruction (compare key to $02 for shift) and we patch into the code the value for the compare. Same for Xshift. If the RDF is wrong, it'll read a value of some other random piece of data and will IR will dutifully report it to you.
but having the remote change the Xshift value would be very, very odd.
I've found a sure-fire way of getting the macros to fire with each press of shift-key. After firing off a macro, press any key that makes the device LED light up. Then I can use the shift-key macro again.
