So the behaviour does NOT occur, as you write:Kruskal wrote:
Any IR file will show as Hex the previous value when creating a Pause button.
but seems to uniquely occur on YOUR computer.
Capn Trips, I've seen exactly the behavior he's describing if I do the following:
1) Open a file in IR that has some special protocol functions defined.
2) Double click a special protocol function, and check the Hex checkbox if it's not already checked.
3) Close the Special Protocol window for thie function.
4) Click Add
5) Choose a special protocol type and make sure Hex is checked.
At this point, the Hex text box should be populated with the last used hex command.
Right -- there is a misunderstandng. I wasn't saying that the Hex value of a defined key changes. I said that the default -- initial -- Hex value when I define a new key changes.
Further, it started with that four-byte value when I created my first Pause key ever.
So what you're saying is that under a unique set of circumstances, when you are creating a NEW Special Protocol keymove, upon initially opening the Special Protocol window, the Hex command field is populated by the Hex values from a previously created SP keymove, regardless of that Hex sequence's applicability to the current keymove you're building.
Do I finally understand?
Then it seems a simple solution - type in what you intend to be there. Is anything preventing this?
Remotes: OFA XSight Touch, AR XSight Touch TVs: LG 65" Smart LED TV; Samsung QN850BF Series - 8K UHD Neo QLED LCD TV RCVR: Onkyo TX-SR875; Integra DTR 40.3 DVD/VCR: Pioneer DV-400VK (multi-region DVD), Sony BDP-S350 (Blu-ray), Toshiba HD-A3 (HD-DVD), Panasonic AG-W1 (Multi-system VCR); Laserdisc: Pioneer CLD-D704. Amazon Firestick tape deck: Pioneer CT 1380WR (double cassette deck) (But I still have to get up for my beer)
No, but it could be confusing to a new user who doesn't realize that
the hex code in the text box is the last hex code used, and not some
kind of default. In this case, Kruskal assumed that the pause protocol
used a 4 byte command. Obviously, taking a quick look at the pause
protocol instructions would clear this up, but I can see where he went
wrong.
floyd1977 wrote:No, but it could be confusing to a new user who doesn't realize that
the hex code in the text box is the last hex code used, and not some
kind of default. In this case, Kruskal assumed that the pause protocol
used a 4 byte command. Obviously, taking a quick look at the pause
protocol instructions would clear this up, but I can see where he went
wrong.
Exactly right. But there was one more thing adding to my confusion. I've run across descriptions of how to program ToadTogs, for example, which are far more primitive than is necessary now that IR provides such a nice high level interface. So whenever I read documentation, I am always aware that it might be at a level lower than currently needed. So when one source indicated that four bytes was needed and the other one byte, it didn't dawn on my that the four bytes was just wrong.