The inevitable has happened: While I did an "ok" job keeping all of my macros organized on a spreadsheet so as to know what macro's I've used and which macro's I still have available....it's....a mess. Surely there has to be a better way to keep it all organized. Perhaps some of you even have some sort of magical way to have KM sort of automatically assign a macro to an available keyswitch or something like that? I think you guys know what I'm trying to figure out here.
Objectively - is there a way to generate an automatic list from KM that shows you what has been used and what is still available?
IMO, the best way to pick a hot key is to assign whatever makes sense to you -- since that'll make it easier to remember -- and the Conflict Palette will let you know if there's a clash.
Otherwise, whether a particular key combo is available will depend on the context in which you are trying to use it. This will output a tab-delimited list of all the hot keys and associated macro names/UUIDs that trigger macros in the current context:
Alternatively, this will get you the same list for all enabled hot key triggered macros -- edit line 5 of the AppleScript to get disabled macros as well:
See this discussion: Keyboard Layout Blank List/Spreadsheet . I mention there that I just keep a list of hotkeys (covering KM and other applications), which is simpler and more flexible than maintaining a full spreadheet. Other solutions are also suggested in that thread.
I can't say I do for that part. Surely you would want to make an informed choice about which hotkey to use, from your pool of unused ones.
Adopting a consistent, logical approach to choosing hotkeys will make the task easier, and the preferred choice each time more obvious.
Consistent and logical just aren't in my vocabulary!
I did do a spreadsheet. If anyone wants it I'll post it to the forum for anyone to use. I did it in Excel. I have never used Excel before so it's probably kind of rudimentary, but at least it sort-of works.
Coincidentally allot of the DAWs are now implementing features that make all of this unnecessary. And the omnipotent OSC adds like a zillion new ways to control things.
Now we're talking! VERY helpful macro ("Display Names and Triggers of All Keyboard Maestro Macros"). VERY, very helpful and brilliant. Thank you for that.
I'm wondering if it might be able to be taken a step further: pray tell, is it even remotely possible (and I'm guessing that it isn't?) that there might be something so convenient as a comprehensive list of ALL macros (available, taken or otherwise) listed out in a list form, with the ones that are being used indicated?
So:
Every single macro combination listed out.
Indications of which ones are taken and with what.
I'm a little puzzled by your question, since the macro you are citing does exactly that. It lists ALL macros. It separates the name of the macro and its trigger with a Tab. If you copy and paste its output into a Numbers spreadsheet, you can sort the spreadsheet by the Trigger value (eg, hotkey), and you will see the shortcuts of all the macros that have hotkey shortcuts all together with their shortcuts.
I just tried it, and it worked for me. If that's not what you want, please clarify what you want. Perhaps show a short sample output list so we can see what you want.
No -- but why would you want to know about my, @Airy's, or anyone else's macros?
If you mean all the macros in your KM Editor, regardless of trigger, and including those that are not enabled -- sure. But you will have to let us know the output "columns" you want.
I suspect you mean "trigger key combinations" rather than macros. Even on a standard keyboard that's more than 1,100 possible hot key triggers times 13 different "types" (pressed, released, etc) plus at least as many "USB Device Key" triggers.
But you're missing an important point. You only "need" to find unique triggers for globally-available macros -- and not even then, because of the Conflict Palette. But many of your macros will be particular to one, or a set of, app(s) or even specific windows (like a certain site open in Safari). So you can use the same trigger for multiple macros if you "scope" your Macro Groups properly.
That's how I understood the question. I gather that my clarifying edit to the subject line of this thread wasn't picked up on in general, and I learn from this for next time.
Have not been on this forum in so long, but I ended up doing a TextEdit sheet that lists everything in Keyboard Maestro, Osculator (for OSC) and for my DAW's key-commands.
It's really a pain, but it does help prevent all sorts of crazy conflicts.
I should have done a spreadsheet, but I've never used Excel before and wasn't about to just start figuring that out now?
