KeyCommand Utility - Now Testing Mac Support

Thanks. I’ll have another go at it.

@SteveInChicago, did you ever get it working on mac?

No, I could never reverse engineer the VB parsing script to implement that column for the extra modifier key.

Mac: shift, ctrl, opt, cmd
Win: shift, ctrl, alt

If this were redone in javascript instead of Visual Basic it could work on both platforms. It requires more advanced scripting than I am familiar with currently, though I might have another go at at at some point.

Hmm let me think about doing a js version. Someone else has asked me for a Mac version. I just stayed so swamped these days.

That would be great.

I played with this this morning, but javascript doesn’t easily support the access to local files. I found a way to do it with ActiveX and other custom solutions, but none of them are cross platform, cross browser compatible. I think perl or python might be easier to make cross platform.

Wonderful, thank you, that’s pinned to my taskbar.

would someone please pm me their keycommands.xml file. I want to work on the perl script, but I’m on the road and didn’t bring it with me. grrrr … dumbass mode engaged.

pm sent. Thanks!

got it!

If you’re working on a new version, how easy would it be to keep the column headers visible when scrolling down?

I’ll look at that if I can get it to parse in perl. I’m not sure if there is a control in HTML5 for that or not.

and it would be great to allow better customisation to separate style and data in the html result by using css

Great utility btw

SeeWhat

I was thinking frames but I may be way out of date with that

As far as I know iFrames don’t work that way, they scroll with the rest of the page. You can control visibility and stuff like that, but I don’t think you can have a split page. But, it’s been awhile for me too. So, that setting may be there.

Just been for a dig in the old machine and this is what I was talking about:

The headings go in title.htm, the rest in text.htm which will be scrollable. Could be deprecated by now for all I know. Anyway, that’s was the idea. Hope it helps. Cheers, C

It’s easy enough to try. I’ll give it a go when I get done with the parsing.

It works by the way, but there is a problem keeping the column widths in synch when the keymap updates. I didn’t want to hardwire the widths, but I’ll play with it some.

I’ve just got to get the key/value pair loop working. I get weird results from the pair pull right now. But, I’m sure it’s just a syntax foobar on my part. So, I’m fairly close. Can’t work on it today/tonight. Maybe I’ll have something this weekend.

Just an FYI, this is going to be in Perl, so you have to have perl installed to run the script.

With Steve’s help we made progress on the Mac version. Still have a path issue to solve, but the basics seem to work. As soon as I get the path thing figured out, I’ll post for general consumption/testing.

I have a 2nd version in progress that splits the column headers so they don’t scroll. However, they don’t retain their size in relation to the each other. So, have to figure that out. I want to get the regular version working before i tackle that.

Well, my humble contribution to this thread… :blush:

As I wanted something quick and using as less resources as possible, I focused more specifically on a .txt format result to be used with Notepad. So, to be able to quickly display all my current key commands in one window, I rebuild a .vbs script from scratch. Sadly, this won’t work on Mac, as it uses the Windows integrated VBScript feature…

So, here it is (the ‘how to’ is in the CubaseKC100_ReadMe.txt in the attached zip folder). The script will show the current key commands settings as soon as the [OK] button of the ‘Key commands’ windows has been used. Hope it will be as useful for some of you as it is for me…

EDIT - CubaseKC101 : a little fix for a more efficient display of key commands related to preferences…

EDIT 2 - CubaseKC102 : a fix that should allow the display of the remaining few keys that weren’t until now, due to an improper encoding (UTF-8) of the script. The script has been reencoded in ANSI and it seems that shift+keys combinations using the five keys just at the left of the Backspace-Return-RightShift block are now also displayed as expected.

EDIT 3 : updated version, see here : Three thingies that could help... (Windows only, sorry...) - Cubase - Steinberg Forums.