On December 13, 2005 at 17:15, triple B said...
The problem I see, as johnsfine already stated,
is that since there is no way to add direct hex
editing into the editors themselves,
Yes I said that
the best
you can do is end up with what is already available.
But not that.
A standalone app that takes in a HEX code and
spits out a CCF which can then be used in the
Universal Browser, to me this is the best solution.
Simply because the editors will all accept the
same CCF as input. However, if you wanted to create
MXD, MXA, RCC, etc, you will have to decipher
all of those formats
I've used only the MX-850 editor (no other URC software), and I just understand where MXD fits in. So I thought a path directly to MXD would be better than going through CCF and the universal browser.
Are you saying for other URC remotes having an MXD file would not be as useful as having a CCF file? In other words, why "all"?
instead of the already well
known CCF format.
Not well known to many people. I know CCF format well enough to read IR signals from it (DecodeCCF.exe) but not nearly well enough to rewrite IrPanels. IrPanels is seriously in need of rewrite, but the source code was never posted.
Of course I know mxd format much less than I know CCF format. But MXD format is simpler.
Maybe I will get some spare time to read up on
the Pronto HEX information. Anyone point out a
good place to start ?
There are two documents, the clear but incomplete one by Barry Gordon
[Link: remotecentral.com]and the unclear but much more complete one by Eigeny Oulianov
[Link: home.tiscali.nl]
