|
JP1 Remotes
|
View previous topic :: View next topic |
Author |
Message |
Nils_Ekberg Expert
Joined: 02 Aug 2003 Posts: 1689 Location: Near Albany, NY |
Posted: Tue Oct 14, 2003 9:43 am Post subject: |
|
|
gfb107 wrote: | Nils_Ekberg wrote: | 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.
Quote: | 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 _________________ Nils
Files Section
Diagnosis File Section |
|
Back to top |
|
|
gfb107 Expert
Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC |
Posted: Tue Oct 14, 2003 9:52 am Post subject: |
|
|
Nils_Ekberg wrote: | 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 : _________________ -- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST) |
|
Back to top |
|
|
Nils_Ekberg Expert
Joined: 02 Aug 2003 Posts: 1689 Location: Near Albany, NY |
Posted: Tue Oct 14, 2003 10:51 am Post subject: |
|
|
gfb107 wrote: | 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.. _________________ Nils
Files Section
Diagnosis File Section |
|
Back to top |
|
|
gfb107 Expert
Joined: 03 Aug 2003 Posts: 3411 Location: Cary, NC |
Posted: Tue Oct 14, 2003 12:22 pm Post subject: |
|
|
Nils_Ekberg wrote: | 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. _________________ -- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST) |
|
Back to top |
|
|
Nils_Ekberg Expert
Joined: 02 Aug 2003 Posts: 1689 Location: Near Albany, NY |
Posted: Tue Oct 14, 2003 1:08 pm Post subject: |
|
|
gfb107 wrote: | Nils_Ekberg wrote: | 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 _________________ Nils
Files Section
Diagnosis File Section |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|