Page 1 of 2
keymap-master v8.03 available!
Posted: Fri Dec 05, 2003 6:30 pm
by Mark Pierson
The latest version of KM (
v8.03) is available.
The only real change is (hopefully) fixing the Run-Time error encountered by Excel 97 users. I could not test this to confirm (XL97 is at work and I won't be back there until Tuesday), so any feedback would be appreciated.
Re: keymap-master v8.03 available!
Posted: Fri Dec 05, 2003 8:45 pm
by mr_d_p_gumby
Mark Pierson wrote:I could not test this to confirm (XL97 is at work and I won't be back there until Tuesday), so any feedback would be appreciated.
It works OK for me in XL97 now, so I think it will be OK for others as well.
Posted: Sat Dec 06, 2003 2:06 am
by silron1
Also works great for me with XL'97 - many thanks for resolving the issue so quickly.
Ron
Re: keymap-master v8.03 available!
Posted: Sat Dec 06, 2003 4:44 am
by Mark Pierson
It works OK for me in XL97... works great for me with XL'97...
Some of the best news I've had all week!
Posted: Tue Dec 09, 2003 9:03 am
by gfb107
Mark,
Does it make sense to remove KM's "save as RM upgrade" feature, since RM's "import KM file" code does a better job?
RM does a better job only because there's more information in the KM file that RM can use to figure it out than the RM file allows.
Posted: Tue Dec 09, 2003 6:23 pm
by Mark Pierson
gfb107 wrote:Does it make sense to remove KM's "save as RM upgrade" feature, since RM's "import KM file" code does a better job?
To be honest, I don't have any opinion one way or the other. It doesn't take up much overhead since it's all done in VBA, but if you really think RM is better at importing, I could remove the feature.
Posted: Tue Dec 09, 2003 7:07 pm
by gfb107
Mark Pierson wrote:gfb107 wrote:Does it make sense to remove KM's "save as RM upgrade" feature, since RM's "import KM file" code does a better job?
To be honest, I don't have any opinion one way or the other. It doesn't take up much overhead since it's all done in VBA, but if you really think RM is better at importing, I could remove the feature.
RM definetely imports a saved KM upgrade better than it loads a "save as RM" KM upgrade. This is because RM can make use of the positional structure inherent in the format of the KM saved file. This makes it possible to better match buttons, particularly in those cases where KM has different button names for different device modes. In the "saved as RM" format, the only identification for a button is the button name, which isn't always consistent across device types.
I also think having only 1 way to convert file formats will reduce support issues.
Posted: Tue Dec 09, 2003 7:13 pm
by Mark Pierson
gfb107 wrote:RM definetely imports a saved KM upgrade better than it loads a "save as RM" KM upgrade.
I also think having only 1 way to convert file formats will reduce support issues.
Gee, and I just made the RM button more prominent on the Setup sheet 8)
I'll remove it for the next release (and it's gonna cost ya big if you ever want it returned!).
Posted: Sat Dec 13, 2003 7:05 pm
by David_Levin
I guess it's just me...
Loading 8.03 into Excel 97 open up the Microsoft Visual Basic Debugger with a pop up....
Compile error:
Can't find project of library
Another window shows:
=================================
Code: Select all
'check for Analysis Toolpak installed (English version only)
If Application.International(xlCountryCode) = 1 Then
If Application.AddIns("Analysis ToolPak").Installed = False Then
msg = ""
msg = msg + "The Microsoft Excel Analysis Toolpak must be installed and" + vbLf
msg = msg + "enabled for keymap-master to function properly." + vbLf + vbLf
msg = msg + "Please use the Tools, Add-Ins... command to enable it and" + vbLf
msg = msg + "then re-open keymap-master."
MsgBox msg, vbOKOnly + vbInformation, kmApp + " - Analysis ToolPak Required"
'close the file and exit
=================================
is highlighted
Posted: Sat Dec 13, 2003 10:32 pm
by usblipitor
Is this the first time you are using KM?
Before the very first time you use KM ever, you have to install the analysis toolpacks as describbled in the KM readme that comes packaged with KM. The following is a quote from the readme that comes with KM:
README FILE THAT COMES WITH KM wrote:KM REQUIRES the Microsoft Excel Analysis ToolPak to function
properly. Go to Tools, Add-Ins..., and make sure the "Analysis
ToolPak" is checked (for specific details, see the Microsoft
Excel help file). If you're using a non-English version of Excel
and/or the ToolPak, please see the "ToolPak Notes" section below.
Usually this means spending about an hour finding the Excel discs which you may need when installing the toolpack. The program is well worth it BTW! Hoppy Hippodays!
Posted: Sat Dec 13, 2003 11:19 pm
by David_Levin
usblipitor wrote:Is this the first time you are using KM?
no, I've run it many times - I can switch to 8.00 and run it without problems.
Thanks
Posted: Sat Dec 13, 2003 11:49 pm
by usblipitor
David_Levin wrote:I can switch to 8.00 and run it without problems
Oops on my part! My Bad! I just saw that toolpack message and found my foot was in my mouth!
Posted: Sun Dec 14, 2003 5:13 am
by Mark Pierson
David_Levin wrote:Loading 8.03 into Excel 97 open up the Microsoft Visual Basic Debugger with a pop up....
Compile error:
Can't find project of library
I assumed that when the guys above reported that the other error was gone, all was well.
I haven't got a clue where to start looking, and no way to track it down for at least a few days.
Posted: Sun Dec 14, 2003 6:28 am
by Mark Pierson
David_Levin wrote:Loading 8.03 into Excel 97 open up the Microsoft Visual Basic Debugger with a pop up....
Compile error:
Can't find project of library
Can you try
v8.04 and let me know if you still get any errors?
Posted: Sun Dec 14, 2003 10:52 am
by David_Levin
Mark Pierson wrote:Can you try
v8.04 and let me know if you still get any errors?
Still didn't work - exact same error - I don't know if it's just my setup. If I'm the only one complaining manybe it's on my end....
Excel 97 SR-2, Win XP Service Pack 1
Here's the Debugger Screen that pops up:
http://home.earthlink.net/~dlevinsprint ... _error.JPG
(view it full size to make it visible)
