On August 24, 2006 at 14:17, NDiNardi said...
I guess johnsfine is telling
me that now i have to translate my hex number into a decimal
number. hmm.
One easy way to do that is with Windows calculator in view/scientific mode.
Another easy way is with Excel, after enabling the analysis toolpak, using the hex2dec function (but only worthwhile if you have some other reason for organizing the data in Excel).
If you aren't going to use IrPanels, then yet another alternative is to see the section in the MakeHex readme about labeling the functions in hex rather than decimal. But even if the MX editor allows direct pasting of Pronto Hex, I think dragging a numbered button from a CCF is easier than finding, copying, and pasting a hex string from MakeHex's .hex output file to the editor.
For shnakz69 and/or anyone else confused over this detail: The Pronto Hex string itself is of course always in hex. No one is interested in translating THAT to decimal. It is the function number (which in IrPanels becomes the button number) that may need translation. The PDF file lists function numbers in Hex. MakeHex by default labels Pronto Hex strings with function numbers in decimal, and IrPanels only works if the Pronto Hex is labeled with function numbers in decimal.
I sure wish someone would build a version of IrPanels with Hex labels, because more manufacturers publish such PDF files with function numbers in hex than do so with function numbers in decimal.