JP1 Remotes

FYI, I just uploaded KM v8.21, which has embedded Notes support.

I uploaded a new version.

I could not replicate your results. However I added some code to strip out as many extraneous characters as possible.

Try it...

I can't figure out where in KM8.21 I add the notes for the upgrade. I opened an existing upgrade in KM and there are already notes for the Upgrade

Ok..I figured it out. It wasn't clear to me that it was the text above the buttons. I kept thinking it should read the info from the notes section.

Now I can't figure out where to add protocol notes

e34m5 wrote:I can't figure out where in KM8.21 I add the notes for the upgrade.

As you have discovered, I'm using the 'Upgrade Description' from the Setup sheet as the note for the device code.

Now I can't figure out where to add protocol notes

You can't. I'm just using the displayed protocol name as the protocol note. The only exception to that is if the user is using Manual Settings. Then the protocol note becomes:
"Custom Protocol for <dev_type>/<setup_code> <upgrade_description>"
i.e.
"Custom Protocol for CBL/1476 GI Cable"

This way, the protocol can be tied back to the upgrade via the note for future reference.

For reference, the key move notes are the actual function name, followed by the functions Description/Notes, if one was entered on the unctions sheet. So, if you have a function labeled "TV/Input" and a note for that function that reads "Toggles ANT/LINE1/LINE2", the embedded note becomes "TV/Input: Toggles ANT/LINE1/LINE2". If no Description/Note was entered, it would simply be "TV/Input".


The reason I chose this approach for notes from KM was so that device and protocol upgrades were at least labeled for future reference. I didn't see a need to make them any fancier than that, since the user can still manually enter any additional notes they desire.

e34m5 wrote:However I added some code to strip out as many extraneous characters as possible.

I think you're stripping out a few too many characters!

Notes for a device without any key moves aren't appearing. If there's key moves, then the note for the device appears. Protocol notes seem to be ok, as do the key moves.

I pasted this and it worked fine

Upgrade Code 0 = 25 C4 (VCR/1476) GI Cable 0476 TEST
C4 08 72 FE 4C 61 B0 70 F0 D0 30 50 C8 98 0C 2C
AC 6C EC 88 CC 5C DC 48 A8
End

Odd... works for me, too. But this doesn't:

Upgrade Code 0 = 00 00 (Cable/0000) TEST Device Upgrade
5A 00 01 00 FF FF
End

I don't have access to the code right now (using a diffetent PC to check stuff)

It didn't work for me either...I can't swear but I think it may have something to do with all the zeros...I'll check the code as soon as I can..

See latest.

It was the 0000 that was breaking it. It was a formatting issue. IR when doing an integer to sring conversion was taking 0000 and converting to 0.

This made the rest of the code very angry. I made so it always formats it to 4 characters.

Should be ok now....

Mark...as soon as you are ready I'll package 5.01 and uploaded.

The device and protocol notes seem to be fixed.

There appears to be an extra space character at the end of the note. Not a big deal, just thought I'd mention it.

Everything else seems to be working the way it should.

er...Houston...are we a go for launch 8)

I guess it's ready for primetime, but that's really you're decision.

If you do release it, remember to update the version number since it still shows as 5.0.0. And while we're on the subject of version numbers, I think you ought to start versioning every release to avoid confusion as to what the current release and betas really are.

I'll change it to 5.01...and version every release henceforth.

I'll make a note that 5.01 can be used in conjunction with KM 8.21...

Tx for all your help...now on to the next project...any ideas 8)

e34m5 wrote:now on to the next project...any ideas

You should probably look into Rob's request.

I'm trying to add support for this in RM. In the process, I think I've found a bug. If the setup code associated with the new device upgrade isn't already assigned to a device button, IR prompts to assign it, but the keymove notes don't get imported. If the setup code is already associated with a device button, the notes do get imported correctly.

Here's a sample device upgrade for a 15-1994 that was generated by RM:

Why yes you did. When Mark and I tested the importing all the info for Keymoves was uppercase. RM creates them in lower case.

I added added code to account for that. See IR 5.02.

Thanks.