Remapping Microsoft Teams keyboard shortcut for mute Topic is solved

[boardtc]

So in Microsoft Teams,Ctrl+Shit+M mutes.

I want this to be handier so I tried a remap to CapsLock:

Code: Select all

^+M::CapsLock

On a test call in Teams, neither capsLock nor the original shortcut works, however

p.s. in case anyone mentions it, on The Scripts and functions forum there is a script for toggling the mute, that myself and other users could not get to work.

[gregster]

I don't use Teams, but it sounds like you want this (press Capslock to send the shortcut/mute):

Code: Select all

CapsLock::^+m	 	; or:  Send ^+m

If you really want to send Capslock instead, when pressing that key combo, rather this:

Code: Select all

^+m::Send {CapsLock}

With your code above, you would actually send ^+CapsLock, because remaps don't release modifiers (but send does).

[boardtc]

So this wired article is completely wrong?

[boardtc]

I don't use Teams, but it sounds like you want this (press Capslock to send the shortcut/mute):

Code: Select all

CapsLock::^+m	 	; or:  Send ^+m

Thanks, this worked in Teams!!
The second option did not.

Can't believe the wired guy put it in the wrong order for remapping.

[gregster]

No, I just checked This actually would work to toggle Capslock:

Code: Select all

^+!n::Capslock

But only because Capslock doesn't seem to care if modifiers are still down. It toggles anyway.
But you shouldn't expect that other keys will work the same way.

[gregster]

Can't believe the wired guy put it in the wrong order for remapping.

He didn't. This is also correct:

let’s say you keep accidentally hitting Caps Lock when you mean to hit Shift, and you’d like to remap it so both buttons are Shift keys. To do this, you would only need the following line:

Capslock::Shift

Pressing Capslock triggers now Shift.

The second option did not.

Like I tried to communicate: The second "option" would do something else completely than the first one.

[boardtc]

Ok. ^+M::CapsLock does not work in Teams for me but CapsLock::^+m does!

[Jim Dunn]

Ok. ^+M::CapsLock does not work in Teams for me but CapsLock::^+m does!

Yes, that's because you want a press of Capslock to be remapped to send ^+M

in the wired article, where he says:

So, for example, in this line:
^+!n::Capslock
The keyboard shortcut Ctrl-Shift-Alt-N would now be mapped to Capslock. Which you’re much less likely to accidentally hit.

He has Capslock on 'the other side' because he wants ^+!n to be remapped to toggle Capslock and, as pointed out above, that does actually work (it's horrible, imo - but works)

I can see how it might have confused you seeing CapsLock on 'the other side' in an example - but that's because, there, he is mapping in the opposite direction to what you want.