JP1 Remotes

The latest version of KM (v8.32) is available.

Changes include:

• Fixed minor bug saving more than 4 entered device/sub-device codes.
• Added check for valid KM .txt file formatting during LOAD and IMPORT.
• Removed 'com/skip' button from '9910/8910/HTPro'.

Mark Pierson wrote:The latest version of KM (v8.32) is available.

Changes include:

• Fixed minor bug saving more than 4 entered device/sub-device codes.
• Added check for valid KM .txt file formatting during LOAD and IMPORT.
  
• Removed 'com/skip' button from '9910/8910/HTPro'.

Why? My 8910 and both of my HTPros have a COM SKIP button that I program/use regularly just fine. Is there a different version of these remotes without that button?

Capn Trips wrote:Why?

Because of this post by Rob.

Oh, OK then. (Good thing I use the extender and RM - mostly - although I frequently use KM as well).

I don't know if anyone ever pushed this level of detail into the RDF files, but we have an RDF file syntax and code in RM so that RM could know these subtle differences between the way an upgrade (in this case it's associated KeyMoves) can be built for extended vs. non extended instances of the same remote.

I assume it is not worth the effort to put the same thing into KM. These issues rarely come up.

The RDFs for the extended and unextended 8910/9910/HTPro do not currently distinguish this behavior. It would be a simple change for Nils to make to the extender RDF to flag the comm/skip button as MoveBind restricted. Does the restriction also apply to the shifted state?

I already added the MoveBind after reading this post. It will be uploaded with the next RDF distribution.