Some of the functions have keyboard shortcuts, and some just don’t, but even for the ones that do, they are not universal shortcuts, which means they only work when Teams is the foremost app, and has the focus. Microsoft Teams is an app built with Electron, so it’s not a “real” Mac app, which makes it more challenging to script. This helps ensure you don’t accidentally trigger this macro without specifically meaning to. So the first key on the macropad sends hyper + 1, which the OS sees as ^⌥⌘⇧1. This makes it easy to create a unique key combination that you can attach a script or macro to. On Mac, the OS sees the hyper key press as sending ctrl + alt + cmd + shift ( ^⌥⌘⇧). The QMK firmware I created (not as hard as it sounds) binds hyper + to each key. I programmed my macropad so that each key is bound to a unique key code combination, that does not already exist on my (65% mechanical) keyboard. So I have 6 keys I can script for Teams functionality. The macropad kit I built is called “3x3Macropad”, but in the configuration I built, it has 2 rows of 3 keys each, a small OLED screen, and a rotary encoder (a knob). (If you are on Windows, I understand AutoHotkey can accomplish much of the same functionality, but that is a story for someone else to tell.) If you do use a Mac, I would strongly encourage you to invest in Keyboard Maestro to make your life better. If you just want to grab the macros and run, you can skip to the end Tl dr I used the wonderful-but-Mac-only Keyboard Maestro (KM). To help you avoid the same fate, here is some detail about how I accomplished this. Unfortunately, the post did not go into much detail about the specific functionality that was implemented. Then last week, there was a Reddit post about using a macropad with Microsoft Teams. This was a fun project, but I never really had a specific purpose for it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |