Is there already a program to convert the hex output from MakeHex to a csf or ccf file, other than IRPanels? I didn't see anything, but I'm not sure if this new program is redundant or not...

I wrote hex2csf to convert the output from MakeHex to a CSF script file that can then be converted to CCF by CCFTools. It is a Win32 command line utility that will convert 1 or more hex files to 1 or more csf files, creating up to 16 panels before continuing in another csf file. Currently, it takes a list of files as parameters (plus a few options) and fills as many panels with text buttons as it needs to for each hex file, and as many panels/csf files as needed to process all the hex inputs. If this sounds useful, I can upload it to the files area once I've tested it a bit more. To make it more useful, I have a couple questions:

In a CCF file, how many a) devices, b) panels, and c) buttons can there be? Would anyone else find this useful?

Thanks!

- Andy

1) Can you clarify the advantage vs. IRPanels?

2) I don't know about limits on buttons, panels, or devices. Are you wondering about limits in CCFTools, or in ProntoEdit, or in the Pronto's firmware? Are those limits hard to test for? I'd think you could just generate a big CSF file and try it. I think the end user would want one ccf file, not one for every 16 panels.

3) What sort of navigation do you provide (I'd expect some sort of hierarchy of panels giving ranges of command numbers dispatching to panels of actual commands).

4) Can you include a .bat file to wrap up the whole process? It seems excessive to need to run MakeHex, then hex2csf, then CCFTools to get from an .irp file to a .ccf file. The user should be able to ignore the intermediate steps.

IRPanels doesn't seem to be able to be used in a batch. I may simply not know how to use it effectively, but it seems like you have to cut & paste the hex codes into its dialog box. It puts only 25 buttons per panel. You can't easily process more than 1 hex data file through it. With 16 panels per file currently, I can end up with just 2 ccf files for all RC5 codes (devices 0 - 31) in raw format, for example -- makes it quick to generate clean codes for copying to remote buttons, such as in the MX-700 editor. (The files area currently has an RC5 ccf file, but they are not in raw format, so are not copyable for me.)

Edit -- I forgot to say that you can drag & drop the data file to the exe, like you can with MakeHex.


I'm wondering what should be a reasonable limit, if there are no hard limits. I can do some testing to add multiple devices instead of outputting multiple csf files. I _thought_ I received an error when trying to add more than 16 panels for 1 device.


For now, the Device is simply "Codes" & the panels are broken up by the name of the device code. Each panel then holds as many commands as will fit, given the size of the buttons -- which is configurable.


A bat file is easy to create -- I can include a sample one, but the user would have to provide the paths, if they aren't already in the PATH. CCFTools' compiler seems to require the user to press a button anyway, even if it is run from a bat file... still much easier than cut & paste with IRPanels.

- Andy

There is no limit on the number of devices, panels and buttons.

However, Prontos crash on very busy panels (like around 100 butttons and frames).

Thanks -- it now can write as many devices, panels, & buttons as you want, for as many MakeHex data files as you can fit on a command line. I needed easy access to the raw RC5 codes while setting up my remote that is on its way & they are now all in 1 file w/32 panels. (Not sure what the problem with more than 16 panels was earlier.)

Anyone want to try it? If not... oh well, it solved my code generation/access problem. :)

- Andy