JP1 Remotes

[gfb107]

OK, I read Hal's readme. Here's the interesting parts:

[gfb107]

Ron, can you confirm that with the URC-8060, only the buttons highlighted with an orange border in RM are available for use with keymoves and/or macros for a given device type? And that these correspond to the keys that are illuminated for that device type?

I suppose the possible exception to that would be the device keys.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[silron1]

absolutely correct - you can only do 'key moves' on the selected screen(s) i.e those keys circled in orange and the dummy keys added by Nils. If you try a move on the non-illuminated screens - it doesn't happen.

It may help you to know (as if you didn't know already!!) that each device has up to 3 screens availiable to it, accessed by using a scroll button situated between the magic and power buttons - This is not a shift but gives more working buttons for each device. eg TV has 3 screens, VCR has 2 screens, DVD has 1 screen, SAT has 3 screens, AUD has 1 screen, CD has 1 screen.


Ron

[gfb107]

Let me summarize what I think I've learned, and ask some additional questions:

1. Using the remote, keymoves can only be programmed onto illuminated keys. What about using IR? I'm sure it allows key moves onto non-illuminated keys, but I'm guessing they can't actually be used?
2. The illuminated keys for a given device type correspond to the ButtonMap (as shown by the orange border in RM).
3. The remote uses multiple screens with only some keys illuminated on each screen. Is there overlap between iluminated keys on different screens? RM draws a border around all these keys at once, which in effect merges all the screens together?

Maybe the best thing to do would be for you to document which keys are illuminated on each to the TV mode's 3 screens. Maybe that will give me a better understanding of how things work.
_________________
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)

[silron1]

answer to 1- yes IR accepts key moves but they only work on illuminated buttons

answer to 2 - yes

answer to 3 - yes illustrated as follows.

TV Screen 1 (illuminated)
*... 1-2-3-4-5-6-7-8-9-0
*... >10
*... mute
*... vol+ - vol-
*... ch+ - ch-
*... menu
exit
up - down - right - left
ok
*... red - green - yellow - blue
*... M1 - M2 - M3 - M4

TV Screen 2 (illuminated)
*...1-2-3-4-5-6-7-8-9-0
*... >10
av
pp
*... menu
*... ch+ - ch-
*... vol+ - vol-
*... mute
*... teletext
*... red - green - yellow - blue
16:9
*... M1 - M2 - M3 - M4

TV Screen 3 (illuminated)
*... 1-2-3-4-5-6-7-8-9-0
* ...vol+ - vol-
*...mute
*... ch+ - ch-
text index
text expand
text mix
text hold
text off
*... red - green - yellow - blue
*... M1 - M2 - M3 - M4

lines of buttons above prefixed thus * .... do the same action in each screen on which they appear.


Ron

[gfb107]

OK, I have an idea about how to handle this multi-screen thing.

I'm thinking a new [Screens] section, similar to the [ButtonMaps] section, and which also has an entry for each DeviceType, using the same device type index.

Each entry would be a sequence of screen definitions, separated by commas. Each screen definition would be enclosed in braces, also like the ButtonMaps. The first item in the definition would be an optional image file to use instead of the one in the .map file, followed by a colon, followed by a comma separated list of the keycodes for keys that are available on that screen. Each keycode could have an optional text value assigned, which would be a unique display name for that key on that screen for that device type.

For example, given the above information from Ron, we would have: