Eight is a workable number of macros, but the proposed triggers require a great deal of typing for most modifier key combinations. He suggested that the trigger cmd would produce the text symbol ⌘.
KEYCASTR NOT WORKING PLUS
Drdrang has already suggested this idea, using the semicolon plus a few letters as the triggers for the different macros.
If the symbols for eight modifier keys are needed, then eight different macros are needed. One approach is creating a different macro for each of the desired individual modifier key symbols. If this describes the needed set of outputs, what macros and triggers might be needed to produce all of them? It would be cumbersome and hard to remember a different trigger to invoke a different macro for each of the hundreds (?) of different modifier key combinations. Needed outputs would include ⌘⌃⇧ ⌘⌃⌥⇧ ⌘⌥⇧ ⌃⇧ ⌘⇧ and many, many more. If this is correct, then the number of different combinations is quite large. I'm guessing that he might need different combinations of eight modifier keys: Shift, Control, Option, Command, and the four arrow keys. To simplify writing the documentation, I believe that Cognominal would like a simple way to type into his text the symbols for the common modifier key combinations. Perhaps we can make progress by analyzing the problem beginning with the output. I have yet to read the KM doc in extenso and understand all of it.Īlso you ask for the input and the output, but both expressed as a string, they are the same even if the input is the typing of a shortcut and the output the string that documents it. I am not a native speaker and I probably misuse the KM terminology. In one month or two, I will have recouped the time spent learning KM. I already have written some (clumsy) macros that have proven useful. Either way, I will use the macro only as many times I have shortcuts to document but I expect to learn much in the process. Also I think I can solve the problem by writing a vscode extension. I certainly do not ask for 8 hours of support at that price.
KEYCASTR NOT WORKING LICENSE
Or more probably, I am failing to make myself clear.Īnyway even if this particular issue is not solved, when I wake up tomorrow I will buy a license (edit: done). Maybe it is not currently possible/natural in KM so you instinctively try to reframe my problem. I would type a shortcut for my application somewhere thanks to KM and would get in return the string that would be pasted in my documentation to document the said shortcut.
But the very point of this one macro would be to avoid a KM hot key trigger for each of the possible combinations of keys unlike you suggest. 🖥️ macOS status monitoring app written in SwiftUI.Thx.
KEYCASTR NOT WORKING MAC
Easily set Mac Retina display to higher unsupported resolutions A tiling window manager for macOS based on binary space partitioning Unlock your displays on your Mac! Smooth scaling, HiDPI unlock, XDR/HDR extra brightness upscale, DDC, brightness and dimming, dummy displays, PIP and lots more! Intelligent adaptive brightness for your external monitors When comparing keycastr and MonitorControl you can also consider the following projects:
0 kommentar(er)
