On September 25, 2007 at 14:02, Birstall said...
I read somewhere on here that
the MX reote will only take learned commands.
There are several different forms of Pronto Hex. The Universal Browser only understands one of those forms (the most common). When Universal Browser finds that form of Pronto Hex in a CCF file, it will call it a "learned" code. Actually, the form of Pronto Hex has little to do with whether the signal was learned.
A signal may be stored in the CCF in a form Universal Browser doesn't understand (and doesn't call "learned") even though the signal was just learned into the Pronto. A signal created by a program such as MakeHex will be in the form Universal Browser calls "learned" even though the signal is program generated, not learned.
If I import
a Pronto .ccf file into the Univ Browser, convert it to
a hex file
What do you mean by "convert it to a hex file"? I don't think there is any option like that when opening a ccf in Universal Browser.
then drag it to a button, does that constitute
a learned code or do I have to do something else to it?
In Universal Browser, you can simply drag from signals in the CCF to buttons in the MX editor. You don't request any kind of conversion. If the signal is the type Universal Browser understands, it will label it as "learned" and let you drag it. Otherwise it won't.
If you have a CCF with signals in a Pronto Hex form that Universal Browser doesn't understand, you probably can convert to a form it does understand using DecodeCCF.exe, DecodeIr.dll, MakeHex, and Hex2CCF.
[Link: john.fine.home.comcast.net][Link: john.fine.home.comcast.net][Link: john.fine.home.comcast.net][Link: remotecentral.com]Even if the CCF file has the form of Pronto Hex that Universal Browser understands, you may find DecodeCCF and DecodeIR.dll very useful for previewing the set of signals in that CCF file.