Oh, a lot of questions. Let's start.
vickyg2003 wrote:.... But what is the separator, if there are two items in the MISC column of a decode? Is it a comma, semicolon, space?
It is presently a space or a tab. Or several of them. I can in principle add more like semicolon, but I am a bit reluctant on the comma, since it is used in some locales as decimal separator.
And if there are two do they need to be in the order found in a misc column of a decode, or the parameter order of a device upgrade?
order is not significant.
Lintronix is a fairly trivial text format for a single IR signal. Graham (?) introduced it in his version of the IrScope, and in his library ExchangeIR.
Seems to me that this was something that was in IRScope when KevinTimmerman wrote it. Then Graham took over, and really made IRScope indispensable.
Kevin, Graham, any of you want to comment?
Do you want a beta tester for IRScrutinyzer? I'm a brutal tester

, just ask Graham. I can also take these things private. I would love to have a look.
Are you going to withdraw IRMaster when you release IRScrutinizer?
My present plan is to get a first, rough, version of IrScrutinizer released ASAP, instead of a beta test period. Then I will release the final version of IrMaster, probably somewhat ironically called version 1.0.0. (There are some bugfixes and additions, in particulat to the export formats, that I have not published yet.) Also, although IrScrutinizer replaces almost all of IrMaster, the export function is completely different, and the war dialer function is not there as such, but a (normally) much better functionality. So there will likely be someone who prefers the old one.
On the Hex Calc screen, would you consider using LSB instead of reverse in the description field?
Although strictly speaking incorrect, this may be a good idea, since "reverse" is not a concept that will give people the right associations.
In Decodes you sometimes see OEM1 or OEM2 in the misc column. These occur when there is a different value than the 84:8 or the 50:8,
Ir(p)Master only gives out what DecodeIR delivers.
Now since the IRP doesn't have a variable there, the Additional Parameters is not enabled.
Well solved the OEM thing in a way. I just added a new protocol called Denon-V for Vicky, and coded the OEM value as a constant.
Full score! Please note the possibility of giving the variables a default value, and the inheritance mechanism (like in metanec) (in the Ir
pMaster documenation).
Since I don't install my JP1 programs in Program Files, I was able to save the changes, and when I opened IRMaster again, OEM1 and OEM2 were there, but the Additional Parameters enable. So I am missing something here. How do you go about doing something like that?
And if I did install IRMaster in Program Files, where would IrpProtocols be stored?
IrMaster lets you store it/load it from any location, assuming appropriate rights.
I've been burned by the Window's "virtual stores" thing enough to know that installing jp1 stuff in the Program Files area, where you might want to change something like an ini or an rdf is never a good idea. So I always put JP1 tools in my jp1 folder off the root so I can tweak as much as I'd like.
To cut a long story short, IrMaster does everything after the book. You can either install in a normally used area, no admin rights required. Or you can, as administrator, install in Program Files. But as a non-admin user, you cannot overwrite the files you once installed. This is a
good thing. Instead you install your own versions of files you want to change somewhere in your home directory, or somewhere else, where you can write, leaving the original install intact! The silliness starts when Windows (Vista and later) pretends to overwrite the Program Files version, but instead writes the file somewhere in a more-or-less hidden location; with your private version subsequently, more-or-less invisibly, hiding the original file. Microsoft....

, they never stop to surprise... So, just don't try to write to an installation in Program Files, and you will be happy.