First of all, thank you for responding on this Feature Request.
Well, getting back to the first part of your question, my intentions are that - even though you’re right and the most scripting for gathering this type of information is easy - all KM users, especially new users won’t have to dig into scripting for that. Yes it is a good way to start learning scripting, but maybe not in all languages.
And if someone has to write a macro that contains a complex script which will act differently based on such information it will be even better because this person will only have to parse the Variables that are using these Functions and Tokens into their code and let the magic happen by writing less code using still the same amount of information.
While I am interested in learning scripting in various languages and maybe many others not I think this would be a huge benefit from every aspect. An example with a little story form perspective:
[Story on:] You’d probably already know that I am tinkering a lot with AppleScript and Apple‘s Objective-C API’s these days. And in the past there was a big issue gathering hardware based information using ASObjC - it was the release of Big Sur 11.3?! - where the AppleScript code had to be recompiled using Big Sur as OS to detect the right version. Remembering it ? A long time I hand a solution using a Submacro to write the code out to a compiled file - because every script in any language I have is a compiled script - getting the correct Information I wanted.
A friend of mine - the one who recently died (mentioned that elsewhere in this forum) helped me to rewrite the code completely so that I can use this script whenever I need it and always get the right info because the essential code is nested in that script and gets written to a compiled file when needed and afterwards deleted when the infos are offered to the workflow. [:End of Story]
Why I am telling you this? Because this is one example of how such an easy task learning to script for this type of information can be a hassle. especially when you have to get it working for more then one OS Version in a preferred language.
And even all this is working now from with KM 9 and 10 and from Yosemite up to Monterey I wish that such a thing would be possible without the have to in the future of KM and a little bit of a wish that it were integrated earlier because even the fact that I love what I do to learn programming I also sometimes really hate it …
Maybe Apple breaks something again in the near future - we all have to live with it as their customers using their hardware and software products.
But everything that is happening on our side, automated by your fabulous product KM with less more effort brought into custom code we have to write and maintain, is something what I am thinking about is absolutely worth it to put time into integrating as much as possible in form of Functions and Tokens into KM.
As I was mentioning to answer the first part of your question following the other parts as well - maybe I found a way to answer everything and I gave you a little insight what I have done to solve this kind of thing for the usage of KM talking to my hardware.
Now that my fingers hurt my message to you is finished. Thanks putting so much effort and time into Keyboard Maestro‘s Development. I appreciate that.
Greetings from Germany