JP1 Remotes

Standing by.

Don

Despite not intending to, I seem to have introduced some confusion. So, let me try again to clear up several points:

1. I was responding only to pH7_jp1's earlier post. I had not, and still have not, looked at Elizabeth's file.

2. When I referred to "HT mode", I was referring to the eight device ...

At the risk of confusing the issue further, "timed callback" is a general purpose function (despite its "special protocol" moniker) that causes a specified keystroke to be issued automatically upon the next expiry of the backlight timer. It has no knowledge of the purpose of that keystroke, the ...

The "action" occurs just after label L40 in Extender 1 ($FF5A) . I labelled Register RB6 "R_Callback".

Code follows:

L40:
FF57: F6 41 32 CALL LCDOff ; Turn off LCD
FF5A: A6 B6 00 CP R_CallBack, 0 ; *Is timed callback flag set?
FF5D: 6B 07 JREQ L41 ; *No
FF5F: E4 B6 80 LD R_Key1, R_CallBack ...

1. Thanks

2. Your question about whether Toadtog2 and Timed Callback are in the same IR prompted me to take another look at my code. No, they are not (now) both resident in the final 8910 IR. I not sure why but, after first implementing the HT status register using Toadtog 2, I changed the code to ...

If Toadtog 2 is a problem in some remotes, an alternative if you don't have need more than 6 devices for which you keep power status, try using the unused toadtog bits to record HT status (e.g., if only 5 on/off status bits are needed, use the remaining three for HT status - say, h001 for CBL, h010 ...

Thought I'd take a few minutes to see of I could come up with the answer quickly.

First of all, its been 2 1/2 years since I've "mucked about" with extenders. So my terminology may be a bit rusty.

Elizabeth has it almost figured out. Timed callback uses device MISC 1900 and Protocol 1FD. The ...

Capn Trips brought this thread to my attention.

I haven't accessed the forum for some time. Sorry. Nor have I looked at the code recently. But, I'll be happy to help.

"Timed callback" has a number of possible uses. Essentially, it allows programming of a future "automatic keypress". My primary ...

Thanks, Nil. Those are the workarounds I used.

I presume there is some technical reason why the insert/delete functions weren't implemented.

Don

On the Buttons screen, the width of all three rows of function names appears to be governed by the longest of all the function names, not just the names in that particular column. If a function name is long enough, the three colums occupy the full width of the window and no button assignments are ...

After about a six-month hiatus, I attempted to make some mods this morning using the Special Protocol Builder in IR.

Using SPB, there appears to be no way to enter a new command (except as a new last command) into, nor to delete a command from, for example, a DSM - other than by direct ...

These are logical devices. For a fuller explanation, please refer to Section 5 of "The WHAT and WHY of JP1", available from the Help Section of Yahoo!

Yeah boy. Some fiddling. I take then you are OK with the changes. Yes.

But, if you want to do some more fiddling, as I noted last night, there is now extra space below the OK/Cancel buttons - about the same amount of space that was previously between the key-field windows and the hex-display ...

Paul, I gather you found the problem while I was away. I just d/l'ed 5.0 and I can now see the Cancel/OK buttons. (In fact, there's even a little extra space below them.)

Thanks,
Don

Just to make sure I understand. When you open the SPB you can't strecth it far enough in the vertical to make the buttons show up, correct. Not exactly. I can increase the dialog up to the full height of the display. When resizing the window from only the title bar in view, the controls appear in ...