When a Device button or shift_Device or XShift_Device is pressed, I want to get at the button number that's being pressed but not until few macro steps run, and in some situations during holding it down. I'd like to catch the number before some other code clobbers it. How volatile is either one of those in the 8910?
R_Key1 = R80 ; Debounced key
R_Key = R82 ; Key being processed
When is the latest time I can get at it? Or is there some other place where it might be sitting.
How to catch pressed device button number for reuse?
Moderator: Moderators
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
How to catch pressed device button number for reuse?
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
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
Thanks John. I'll try it.
How can I make a keymove that sends no hex code? Just fake something and ignore it?
I just want a protocol to grab and store the button number. I have nothing to say to IR.
How can I make a keymove that sends no hex code? Just fake something and ignore it?
I just want a protocol to grab and store the button number. I have nothing to say to IR.
Precisely what I'm looking for.johnsfine wrote:...through the entire execution of a macro (or extender nested combination of macros)
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
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm