keymap-master v9.14 available!

mr_d_p_gumby · Post by **mr_d_p_gumby** » Sat Oct 04, 2008 1:57 pm

The latest version of KM (v9.14) is available.
Changes include:

Corrected bug in shifted keymove generation on Buttons sheet.
Corrected problem with formula in column E of Functions sheet.
Added support for PID 004B Thomson.
Added support for PID 01B5 Samsung36.
Updated DigitMap entries 441-446.

mappedyr · Post by **mappedyr** » Mon Oct 27, 2008 10:27 am

There seems to be a problem with KM v9.14. When I generate an upgrade for URC-8820 and save it, the program says "This file does not appear to be a valid keymap-master Device Upgrade." when I load the upgrade again. It works in KM v9.12.

Cheers,
Kjeld

mr_d_p_gumby · Post by **mr_d_p_gumby** » Mon Oct 27, 2008 2:07 pm

mappedyr wrote:There seems to be a problem with KM v9.14. When I generate an upgrade for URC-8820 and save it, the program says "This file does not appear to be a valid keymap-master Device Upgrade." when I load the upgrade again. It works in KM v9.12.
Cheers,
Kjeld

I don't seem to be able to reproduce your problem with KM v9.14. Can you upload a copy of your problem file to the diagnostic area and then post a link to it here?

mappedyr · Post by **mappedyr** » Mon Oct 27, 2008 3:59 pm

Hi Mike.

I have uploaded a zip file with two upgrades: One made by KM v9.12 and one by KM v9.14. It seems there is an extra semicolon on the lines produced by v9.14, if that matters.

I use an Excel from Office 2000 and my Windows XP has language set to "Danish" in Regional Options. I tried changing the language to "US English" and then problem disappears.

Cheers,
Kjeld

Post by **vickyg2003** » Tue Oct 28, 2008 7:46 am

Mike I have a question on user error. I'm not quite sure what I'm doing, but I often manage to crash excel leaving the spreadsheet "locked".

I open them for read only, save them with another name, but is there a better way to "unlock" a keymap-master file?

Mark Pierson · Post by **Mark Pierson** » Tue Oct 28, 2008 8:42 am

vickyg2003 wrote:I open them for read only, save them with another name, but is there a better way to "unlock" a keymap-master file?

Sure... don't let Excel crash!

That's an Excel problem for sure. The next time it happens, check the Task Manager to see if the instance of Excel is still running after the crash. If so, terminate the process and see if that helps with the locking problem.

Mark Pierson · Post by **Mark Pierson** » Tue Oct 28, 2008 8:54 am

mappedyr wrote:I use an Excel from Office 2000 and my Windows XP has language set to "Danish" in Regional Options. I tried changing the language to "US English" and then problem disappears.

Back when I maintained KM I spent a ton of time sorting through the various problems associated with international compatability.

This problem seems to be legitimate in KM 9.13 & 9.14 since it looks like Mike made some modifications to the Output sheet in v9.13.

Mike, I think the fix is to move the text from Output!M1 to Output!N1.

Mark Pierson · Post by **Mark Pierson** » Tue Oct 28, 2008 11:37 am

Mark Pierson wrote:Mike, I think the fix is to move the text from Output!M1 to Output!N1.

And the corresponding changes on the Input sheet, too.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Tue Oct 28, 2008 1:48 pm

mappedyr wrote:I have uploaded a zip file with two upgrades: One made by KM v9.12 and one by KM v9.14. It seems there is an extra semicolon on the lines produced by v9.14, if that matters.

I use an Excel from Office 2000 and my Windows XP has language set to "Danish" in Regional Options. I tried changing the language to "US English" and then problem disappears.

Yes, this is the problem. It will only affect language versions of Excel that do not use a comma as the delimiter in CSV files.

Mark Pierson wrote:This problem seems to be legitimate in KM 9.13 & 9.14 since it looks like Mike made some modifications to the Output sheet in v9.13.

Mike, I think the fix is to move the text from Output!M1 to Output!N1.

You are correct; I forgot to move M1 to N1 when I made the change to the saved file format. I'll fix it for the next version for sure!

However, there is still a minor bug in the VB code where a comma is used instead of the actual delimiter character, and that's been there for a while. I can fix this too for the next KM version, but you won't be able to open saved files in older versions because of the bug. A work-around would be to edit the saved .txt files to move the semicolon (in this case) from the end of the first line to before the words "CURRENT DATA".

For example (highlighted in red):

Name:;8820 upgrade KM v9.14;;;;v9.14;;;;;;;CURRENT DATA;
Name:;8820 upgrade KM v9.14;;;;v9.14;;;;;;;;CURRENT DATA

Just for reference, I did make a small change in the saved file format that should have been backwards compatible (except for this bug!). The hex keycodes are saved for each button that has a function assigned to it. This was done so that I could re-order the buttons on the Button sheet in KM. The original button order was locked to the saved file format, and harkened back to the days of the 15-1994. Things like PVR & cable box buttons simply had no logical place to exist, and as a result they were inconsitently assigned on various remotes.

mr_d_p_gumby · Post by **mr_d_p_gumby** » Tue Oct 28, 2008 2:08 pm

Mark Pierson wrote:
vickyg2003 wrote:I open them for read only, save them with another name, but is there a better way to "unlock" a keymap-master file?
Sure... don't let Excel crash!

That's about the best advice I can think of, Vicky. Perhaps Excel is still running, as Mark suggests. If KM crashes in the VB code before it is finished, it will leave it in a state where the screen image will not be updated (hence appearing locked), and automatic calculation turned off. The best way around this is just to shut down Excel and reload Execl & a good copy of KM.

Mark Pierson wrote:Back when I maintained KM...

Yeah Mark, and I bet it was uphill, through the snow, both ways!

Mark Pierson · Post by **Mark Pierson** » Tue Oct 28, 2008 3:15 pm

mr_d_p_gumby wrote:Yeah Mark, and I bet it was uphill, through the snow, both ways!

Are you trying to tell me it isn't?