After the Tahoe upgrade, my keyboard shortcuts work for a short period of time, then whatever is in the clipboard begins pasting in rather than any of my shortcuts.
I saw "reboot" in one of the threads and that works temporarily, but I would like to avoid rebooting several times a day.
It's very difficult to determine what's wrong without seeing your macros.
Do you know how to check the KM Engine log, to see what's triggering? (It's under the KM Editor Help Menu.) Do you know how to turn on the KM Debugger to see what's happening? (It's under the KM icon in the system tray.) Do you know how to turn on "Interactive Help"? (It's under the Help Menu in the KM Editor.) If none of these things help, you should consider uploading your macros.
Oh, I see, I was looking below at the doc
In the debugger I see that if I try to obtain a previously copied text to my clipboard the debugger is showing Activate Clipboard History Switcher... which makes sense since shift/Command/V (what I usually use to paste a historical copy, is also the key command for Activate Clipboard History Switcher... but is that perhaps what is getting stuck after several uses?
Also, with the debugger up, the clipboard history does not appear... is that appropriate?
Exactly! You are learning how it works, that's great.
Everything should work while the debugger is running, but be aware that you can pause macros inside the debugger. That's the whole point of the debugger, to pause things. If you couldn't pause things, the debugger would be nearly useless.
So, I'm wondering if the keyboard command to Activate Clipboard History Switcher could be having issues... it seems like after using it for awhile to obtain historical copies, then when I try to use any macro, it just uses the last paste from the History Switcher.
So, if I've been copying and then pasting from history... example
Copied from document:
This
That
Other
Then shift/Command/V to paste from history select "that" which gets pasted into the document
Then use macro: cR
Instead of pasting from the macro the plain text associated with the macro, it again pasts "that"
But only after I've been working for awhile after a reboot.
I'll grab the logs next time it does that...
Is it a good policy to clear the logs occasionally?
We don't need to see all your macros, but I can't tell you which one(s) you need to upload because I have no idea what they do. Just upload the minimum that you think will let us replicate the problem.
My record isn't perfect. Some days my ideas work, some days they don't. In this case, I didn't have many ideas because I couldn't replicate your problem, and I couldn't see your code.