On January 11, 2022 at 08:47, synapse-md said...
So, if I understand correctly, "1" will be read as decimal and "01" as octal?
Exactly. Possibly better example: "10" will be read as 10, "010" as 8, and "0x10" as 16.
This explains the problem I am seeing -- for many of the codes, I was seeing a different T value from Charlie.
That was to be expected.
It seems that the renderer shifts from T=0 to T=1 if you click "Render" another time with the same input. Do I have this right?
Yes, it is the intended behavior with T left blank. You can of course also fill in a T value explicitly (talking about the "Render" pane).
How does the T value affect the behaviour of the IR code?
It is used to tell a long keypress from a repeated key press of the same button. Unless the toggling is working (meaning that you really have two hexes for every key), you may not be able to (e.g.) turn a TV to channel 11.
