What is 'AllBind' in the FavList?

Support forum for extenders. If you're having trouble getting one up and running, this is the place to come.

Moderator: Moderators

Post Reply
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

What is 'AllBind' in the FavList?

Post by ElizabethD »

In the IR editing tab for FavList there is AllBind command included in the dropdown list.
No docs about it in the 8910ext1 that I can see.
Suggested uses?
Nils_Ekberg
Expert
Posts: 1689
Joined: Sat Aug 02, 2003 2:08 pm
Location: Near Albany, NY

Post by Nils_Ekberg »

It looks like there is an error in the RDF you are using. The AllBind is a command in the RDF to stop users from assigning functions to certain buttons. Compare the original extender RDF from the zip file to the one you are using and see if there is an orphaned AllBind command in the buttons section. For some reason IR is picking it up as a device name.
Last edited by Nils_Ekberg on Sat Jun 25, 2005 5:11 pm, edited 1 time in total.
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

AllBind is a value for restricting what things can be done with a button in IR and RM. AllBind is supposed to mean that you can't bind anything (keymove, macro, timermacro, etc) to a button. Essentially it means the button can only be used in macros, you can't redefine what it does. This is typically used for the DEV_* buttons that have special meaning.

It's presence in the dropdown list means there is a syntax error in the RDF causing IR to think it is the name of a button.

In the [Buttons] section, the line
DEV_DB08[MySys]:AllBind,DEV_DB09, DEV_DB10, DEV_DB11, DEV_DB12, DEV_DB13, DEV_DB14
should be
DEV_DB08[MySys]=$70:AllBind, DEV_DB09, DEV_DB10, DEV_DB11, DEV_DB12, DEV_DB13, DEV_DB14
I hope Nils is watching...
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

Shucks, I thought it was some cool feature to manage three layers of possible devices in the Fav key :eek: .
BTW I don't have a problem to resolve, Fav key is working fine with what I have. I'm just playing with some odd variations.
Regarding versions:
original rdf is from 8/17/2003 in my zip file. I never used it 'cause the instructions always say to use current
EV_TV=$68, DEV_VCR, DEV_CBL, DEV_SAT, DEV_CD, DEV_DVD, DEV_RCVR, DEV_AUX,
DEV_DB08[MySys]=$70
DEV_DB09=$71, DEV_DB10, DEV_DB11, DEV_DB12, DEV_DB13,DEV_DB14
Dev_Cancel=$78
one I'm using, current v121, I think 118 and 120 were the same
DEV_TV=$68:AllBind, DEV_VCR, DEV_CBL, DEV_SAT, DEV_CD, DEV_DVD, DEV_AUD, DEV_AUX
DEV_DB08[MySys]:AllBind, DEV_DB09, DEV_DB10, DEV_DB11, DEV_DB12, DEV_DB13, DEV_DB14
Dev_Cancel=$78:AllBind,
Not sure if to make changes.
This AllBind thing bit me once before,
https://www.hifi-remote.com/forums/viewt ... ht=allbind
and I believe Mark Pauker took care of it, since whatever I was doing then works now. So, I'd hate to break things especially when I barely understand.
Nils_Ekberg
Expert
Posts: 1689
Joined: Sat Aug 02, 2003 2:08 pm
Location: Near Albany, NY

Post by Nils_Ekberg »

It looks right. Could you e-mail me the RDF your are using so I can see why you get the AllBind in favscan and I don't
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

The change I suggested is consistent with the 8/17/2003 RDF, as it adds the keycode back to the definition of DEV_DB08[MySys], which is what was causing the syntax error.

To add more details:

The syntax for a button definition in the RDF is:

[generic name:]name[=keycode[:restrictions]]

where fields enclosed in square brackets are optional.
If the generic name is omitted, it defaults to the name.
If the keycode is omitted it defaults to the one more than the keycode of the previous button and the restrictions default to those used with the previous button.
If the keycode is specified but the restriction in not (restrictions can only be specified when the keycode is also specified) the restriction returns to the default value (which is specified elsewhere in the RDF).

Restrictions were added after I started working on RM as a way to indicate what was not allowed for a given button. Some remotes have some buttons that can't have keymoves, or learned signals, or macros. Also, extenders define special keys (eg DEV_AUX) that can only be used in macros. IR and RM shouldn't allow you to assign things to these buttons.

So, the definition in the current RDF
DEV_DB08[MySys]:AllBind
results in a key with generic name DEV_DB08[MySys], name AllBind, keycode $70 (one more than the keycode of the previous key, all the way back to DEV_TV). and restriction AllBind (the same as the previous key, all the way back to DEV_TV).

The definition I suggested
DEV_DB08[MySys]=$70:AllBind
is a key definition with generic name and name DEV_DB08[MySys], keycode $70 and restriction AllBind.

The difference is just that the name (as displayed in IR and RM) of the key changes to DEV_DB09[MySys]. That's all.

The other choice that would result in the same thing is just
DEV_DB09[MySys]
but we usually include keycodes and restrictions with the first key on a line just for completeness.

Go ahead and make the change to the RDF.
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

Nils, it's on its way.

Greg, thank you SO much for the details in plain English. A while back i dropped out of the RDF class at abut 5th line :wink:
I'll change it, now that I see a bit more what it's about. And yes, you're right, the dropdown list shows AllBind followed by Dev_09.
Nils_Ekberg
Expert
Posts: 1689
Joined: Sat Aug 02, 2003 2:08 pm
Location: Near Albany, NY

Post by Nils_Ekberg »

Greg, I see what you are saying and agree but it does not explain why she sees the AllBind in IR and with the exact same RDF I don't see it in IR.. By the way, I am on IR6.10.
ElizabethD
Advanced Member
Posts: 2348
Joined: Mon Feb 09, 2004 12:07 pm

Post by ElizabethD »

Nils, that's curious. I'm on 6.10 also.
The remote is 8910B02 with arrows, but that can't make a difference.

I looked into old rdf zips I still have. They were not the same as 121. Changed in v120.
RDF 118
DEV_TV=$68:AllBind,DEV_VCR,DEV_CBL,DEV_SAT,DEV_CD,DEV_DVD,DEV_AUD,DEV_AUX
DEV_DB08[MySys],DEV_DB09,DEV_DB10,DEV_DB11,DEV_DB12,DEV_DB13,DEV_DB14
Dev_Cancel=$78:AllBind,

RDF 120
DEV_TV=$68:AllBind,DEV_VCR,DEV_CBL,DEV_SAT,DEV_CD,DEV_DVD,DEV_AUD,DEV_AUX
DEV_DB08[MySys]:AllBind,DEV_DB09,DEV_DB10,DEV_DB11,DEV_DB12,DEV_DB13,DEV_DB14
Dev_Cancel=$78:AllBind,
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

Nils_Ekberg wrote:Greg, I see what you are saying and agree but it does not explain why she sees the AllBind in IR and with the exact same RDF I don't see it in IR.. By the way, I am on IR6.10.
I am also seeing it on IR 6.10, with RDFs 1.22.

You have to scroll all the way down the list of available keys when creating/editing a Scan/Fav macro. It's between DEV_AUX and DEV_DB09, where DEV_DB08[MySys] should be.

It also shows up in the available keys for use in a macro.
Nils_Ekberg
Expert
Posts: 1689
Joined: Sat Aug 02, 2003 2:08 pm
Location: Near Albany, NY

Post by Nils_Ekberg »

I see the problem. I was looking for it in the DEVICE list pull down on the bottom of the scan/fav tab not in the list of available buttons for when you add a mini macro.

So, adding the button code does solve that problem.

Sorry if I created extra work for everyone.
Post Reply