New 6805 RDF's

[Nils_Ekberg]

I actually like the idea of tying the map shape to the button code just not looking forward to making the change but that has been my biggest headache with RDF button names changing. For migration from text to number could you make it both ways or would it have to be all or nothing?

I'll try to make it go either way. The only issue is the digit buttons. I'll assume that a single digit is a name. So, when using keycodes, either use HEX ($xx), or use more than 1 digit.

I assume you would pick up the button name from the RDF based on the button code in the map.

Yes, the display name comes from the button after the match is found. The only exception is when the map file overrides the button name as in URC-43000B01.MAP

Don't knock yourself out making a two way (text and hex code) version since I think it would be too complex and a lot of overhead.. Just make a button code version for me to test with and I will migrate ALL of them before posting any. After I finish the generic name changes I will start to build a set with the button code.

I don't want to have to enter the $ so assume it will always be 2 digits. Trust me he says....LoL

[gfb107]

Don't knock yourself out making a two way (text and hex code) version since I think it would be too complex and a lot of overhead.. Just make a button code version for me to test with and I will migrate ALL of them before posting any. After I finish the generic name changes I will start to build a set with the button code.

I don't want to have to enter the $ so assume it will always be 2 digits. Trust me he says....LoL

The only reason for supporting both hex and decimal is for consistency with the RDF. Some RDFs uses hex exclusively, some use decimal exclusively, and some even mix both.

Would there be any value is prepending the name with the keycode, like

03:Power

This might make it easier to maintain the map files. The name part would not be used for matching buttons, it would just be a comment.

It would also be easier to figure out when a name is used and when a keycode is used, based on the presence of the :

[Nils_Ekberg]

The only reason for supporting both hex and decimal is for consistency with the RDF. Some RDFs uses hex exclusively, some use decimal exclusively, and some even mix both.

Would there be any value is prepending the name with the keycode, like

03:Power

This might make it easier to maintain the map files. The name part would not be used for matching buttons, it would just be a comment.

It would also be easier to figure out when a name is used and when a keycode is used, based on the presence of the :

Do you mean the 03:Power in the map? If so I agree that it would be a good comment field option and easy enough to enter..

[gfb107]

Do you mean the 03:Power in the map? If so I agree that it would be a good comment field option and easy enough to enter..

Yes. As of v0.73, a map file entry MAY specify a keycode along with the button name. The keycode is optional.

If the keycode is specified, it will be used to find the matching button. As in an RDF, the $ prefix is used to denote a hex keycode.

If the keycode is not specified, the button name is used to find the matching button. Otherwise, it is just a comment to help the map file developer/maintainer.

<shape-type> [[$]<keycode>:]<button-name> <shape-parms>

Where
<shape-type> specifies the type of shape: circle, rect, or poly
$ indicate the keycode is in hex
keycode is the keycode of the button associated with this shape
<button-name> is the name of the button.

[Nils_Ekberg]

Do you mean the 03:Power in the map? If so I agree that it would be a good comment field option and easy enough to enter..

Yes. As of v0.73, a map file entry MAY specify a keycode along with the button name. The keycode is optional.

If the keycode is specified, it will be used to find the matching button. As in an RDF, the $ prefix is used to denote a hex keycode.

If the keycode is not specified, the button name is used to find the matching button. Otherwise, it is just a comment to help the map file developer/maintainer.

<shape-type> [[$]<keycode>:]<button-name> <shape-parms>

Where
<shape-type> specifies the type of shape: circle, rect, or poly
$ indicate the keycode is in hex
keycode is the keycode of the button associated with this shape
<button-name> is the name of the button.

And it works also. I even tried to beat your code by leaving off the $ and then the name/comment and it failed both times. Guess the codes too tight HaHa