Shift/Menu on extended URC7562 in IR4.01

DavidLewis · Post by **DavidLewis** » Fri Jan 23, 2004 9:28 am

Hi,

I'm using a URC-7562 with extender, and IR v4.01. I notice that on the "Macros" tab in IR, all shifted keys are displayed as "Menu-xxxx" rather than "Shift-xxxx". When I add a new macro in IR, the dialog box gives me a choice of associating the bound key with either "Shift" or "Menu". I need to select "Menu" for the macros to actually work properly on shifted keys (of course the shift button is actually called "Magic" on the URC-7562). So, two questions:

1. is the apparent swapping of "Menu" and "Shift" a mistake in the RDF file?
2. what does "Menu" actually mean in this context? If I assign a macro to "Menu-REW" for instance, how would I actually play that macro on the remote?

Thanks,
David

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Jan 23, 2004 10:19 am

You may either have the wrong RDF or the menu option instead of shift option is selected on the add/edit macro popup.

wimfabri · Post by **wimfabri** » Wed Jan 28, 2004 8:27 am

I have the same problem with the RDF from the RDF distribution.

The RDF bundled with the extender works OK.

And I also would like to now what the 'Menu' selection is used for.

Thanks to all JP1 developers !

aberguerand · Post by **aberguerand** » Wed Jan 28, 2004 1:22 pm

7560/7562 keys can activate functions in three modes :

- normal (unshifted). Example : Volume Up
- shifted (Shift key pressed before). Example : Bright Up = Shift + Channel Up
- menu mode (Menu key pressed before). Example : OK/Enter = Menu + Mute

Basically, only the Mute (OK/Enter) and AV (Exit) have a specific function assigned to them in menu mode.

Unfortunately the way the codes for the Shifted and Menu modes are stored in the remote are the reverse of what they are in other remotes. The "new" RDF format is supposed to handle this oddity, there have been lengthy discussions about that, but I am not sure how the RDF has been adapted.
I will give a look at the distribution RDF to find out what (if anything) is wrong with it. (BTW, my "old" 7560 is now gathering dust since I migrated to the 6131M).

Alain

aberguerand · Post by **aberguerand** » Thu Jan 29, 2004 4:48 am

aberguerand · Post by **aberguerand** » Thu Jan 29, 2004 5:42 am

I gave a look at the distributed 7560/7562 extender RDF. It contains a small typo at the line :
DefaultRestrictions=XShift should be
DefaultRestriction=XShift

Nevertheless, correcting only this would not make sense, as no menu mode key could then be defined. This default restriction should be removed in the definition of buttons that have assigned functions in menu mode (Mute and AV) ie :
AV{Exit_20}=$18:XShift-XShift;
MUTE{Select}=$08:XShift-XShift;

(Is there a less clumsy way to overide the default restriction ? I tried ":-XShift", but IR complained).

Anyhow, this really is nitpicking, as the handling of the menu mode is only required for RM, in "layout" mode (you could not assign the Exit and Select functions to physical buttons in this mode). For IR or RM in "buttons" mode, functions can directly be assigned to the Exit and Select pseudo-buttons, without needing handling of the menu mode.

So the RDF could also completely ignore the menu mode (as the RDFs for the unextended 7560/7562 do) and still be usable.

By looking at the "new" RDFs, I stumbled on two questions :

- Both the RDF specifications distributed with IR4.01 and located in the Yahoo "RDF Files" directory have the same name (RDF3Spec), but the Yahoo file is really the "old" spec. It should be replaced with the current one.

- Most of the RDF files I looked at do not use the buttons restrictions. It implies that in the unextended remotes for instance, it is possible for the user to assign keymoves to the Shift or devices keys, although this is not supported by the remote firmware. The new RDF specification gives the flexibility to fine tune the user interfaces of IR and RM so that only the assignments supported by the remote firmware/extender are allowed. This fine tuning would however require a lot of work, as the support for each button in each binding mode (key move to and from, macro, learn, fav and all in normal, shifted and xshifted mode) would have to be assessed and implemented in the RDF. I think it would be necessary to define some guidelines in regard to the issue of button restrictions so that a certain uniformity is across the RDFs.

Alain

Nils_Ekberg · Post by **Nils_Ekberg** » Thu Jan 29, 2004 7:20 am

Alain

I will make the changes you outlined for the next RDF distribution. I have not done much in the RDF's with the button restrictions except for the remotes that I have and not even all of them. I need to rely on people who have the remotes and understand button restrictions to make the changes and test them.

gfb107 · Post by **gfb107** » Thu Jan 29, 2004 8:04 am

aberguerand wrote:I gave a look at the distributed 7560/7562 extender RDF. It contains a small typo at the line :
DefaultRestrictions=XShift should be
DefaultRestriction=XShift

Nevertheless, correcting only this would not make sense, as no menu mode key could then be defined. This default restriction should be removed in the definition of buttons that have assigned functions in menu mode (Mute and AV) ie :
AV{Exit_20}=$18:XShift-XShift;
MUTE{Select}=$08:XShift-XShift;

(Is there a less clumsy way to overide the default restriction ? I tried ":-XShift", but IR complained).

I think what you want is "All-XShift" which means apply all restrictions except anything in the XShift state, i.e. only allow XShift.

Does "XShift-XShift" give the desired results in RM and IR? I wouldn't think so. It should result in no restrictions at all.

aberguerand · Post by **aberguerand** » Thu Jan 29, 2004 9:18 am

gfb107 wrote:Does "XShift-XShift" give the desired results in RM and IR? I wouldn't think so. It should result in no restrictions at all.

Yes, it gives the desired result. What I want to do is override the default restriction (which is "XShift") for some keys, so that they can be XShifted.

Intuitive ways to do that would be to define such keys as :

AV=$18: (implicit no restriction) or
AV=$18:-XShift (the default restriction is removed) or
AV=$18:None (explicit no restriction)

Unfortunately, none of these combinations are accepted by IR. So I came to the above mentionned XShift-XShift kludge that is accepted and works. BTW "anything-All" also works.

Alain

gfb107 · Post by **gfb107** » Thu Jan 29, 2004 10:22 am

OK, I didn't get that you were trying to clear all restrictions.

I agree there are some things we can do to make it easier to accomplish things like this.

None - required to simply not have any restrictions, overriding the default.

Default - to allow adding to (or removing from) the default.