I have been capturing bitmaps and using the converter program posted here. I have added half a dozen or so custom buttons and the software will no longer download to the remote. I get a "run time error 9, subscript out of range" error. Anyone see this?

You've added too many buttons... I mentioned this "feature" in my review. You may be under the total number of buttons allowed, but it sounds like you've been using big ones.

Doug,

Where have you been "capturing bitmaps"? I'd like to create some slicker buttons, but I'm sure someone with more creativity than I has already done so, but I don't know where to find them...

I've seen that replacing the mark.btn (which you can only change if you directly modify the MDL file...) will cause this error as well. What I found actually was that the mark.btn had to be at least 12 lines long, any less and the program would crash. All other buttons haven't showed this problem.

Jason

BTW, I was changing the remote to use a different button than mark.btn for the "last page" button. That is why I had to modify the MDL file directly. Normally the program won't let you modify that button. Again, not sure if it works yet because my freaking remote is nowhere to be found!

Too many buttons you say Daniel? That sucks! Is it a memory limitation?? There should at least be a friendly error message of what the problem is. I hope this is fixable, can you elaborate?

It's more of a soft limit.

1) You can have up to 31 total buttons; 8 are system buttons and cannot be deleted. If you try to add another button you get an "out of memory" error.

2) It seems the total SIZE of the buttons also counts. For instance I loaded up all possible custom buttons including two huge ones. When trying to download I received that "subscript out of range error". By replacing those two buttons with smaller ones the error went away. Note it was not the physical size of the button, but rather just how much total memory all buttons encompass.

I would imagine this is a correctable problem. Right now it seems things are divided up into strict blocks:

xx bytes for layouts
xx bytes for learned signals
xx bytes for bitmaps
xx bytes for macros, etc.

What it needs is a flexible file format like the Pronto... just lump everything together and ensure it's under the maximum file size.