You realize many macOS APIs date back to the NeXTSTeP days, right?I don't want macOS APIs get old.
You realize many macOS APIs date back to the NeXTSTeP days, right?I don't want macOS APIs get old.
You realize many macOS APIs date back to the NeXTSTeP days, right?
Yes, it's always best to be as specific as possible, or at least so I've found. One might assume that the next iteration of Scrivener will have the exact same commands, but they changed the implementation on some things drastically, as best I recall, from 2 to 3, and 4, assuming it is created, may do the same.Wow, I didn't know you could enter the menu path too.
I just tried it with "Make Uppercase" and it worked. No need to enter the full menu path. But I can see how that might be a problem if there are two menu entries with the same label that do different things.
you cannot, or at least I haven't been able to edit an existing shortcut.