WinActivate, % "ahk_class " class Switch back to original window WinWait, % teams Wait until teams is actually active WinGetClass, class, A Save current window class name If WinExist(teams) Only run if Teams exists Teams := "ahk_exe Teams.exe" So I don't have to keep typing it ^0::TeamsMuteToggle() press ctrl+0 to toggle mute Now it can switch to teams, send the command to mute or unmute, then snap back to what you were originally working on. Or we can make it a little more versatile and tweak it to remember what window you were on. Here's with window switching: ^0::TeamsMuteToggle() Like the entire "send" portion is extremely verbose with your keystrokes and can be replaced with SendInput, ^+m. There's a lot in yours that you really don't need.
If it doesn't work, you can just alter the function to include the manual window switching.Īs for the "issue with the commands". I've used Teams in the past but don't have an active Teams account right now so no way for me to test it. There's a script that comes with AHK in the main folder called WindowSpy that tells you the info of the window you're working with. Verify that the window name is "teams.exe". SendInput, īypassing a ton of commands is usually preferred and controlsend would've done that. SysGet, MonitorPrimaryVar, MonitorPrimary WindowTitle:="Microsoft Teams ahk_exe Teams.exe" SetWorkingDir %A_ScriptDir% Ensures a consistent starting directory. SendMode Input Recommended for new scripts due to its superior speed and reliability. #Warn Enable warnings to assist with detecting common errors. #NoEnv Recommended for performance and compatibility with future AutoHotkey releases. What I have works, except for the keypress part. I need to hold down to mute my microphone on Microsoft Teams during a meeting.
It seems to me that since all three drivers are provided by Intel, and the two versions that Windows seems to want to use are both broke, the problem seems to be on your end and I'm still left wondering what you are going to do to fix it. Your suggestion to contact Microsoft Support was no help whatsoever.
After the update (and after blowing through my daily cap) the date was (both said the driver provider was Intel Corporation).Īlas, my rotation was still not working so I reverted to the driver from (also Intel Corporation). Prior to this action, the driver date was. In spite of the fact that an update had just been applied (I assumed the latest and greatest) I went to the device manager, selected Intel(R) HD Graphics 520 and clicked "Update Driver". Once again it killed my ability to rotate the display. Last night another driver update was forced onto my laptop. Please let me know the results of installing the drivers above.Īny further questions, please let me know.
If the problem persists you can try to install the drivers manually: Since the laptop works with Intel HD Graphics 520, if the problem remains after trying the drivers above, we can try the following Intel drivers: In this case we recommend to use the drivers provided by Dell, not sure if you are using Windows® 10 but on the link below you will be able to select the operating system, look for video: In order to recover that feature, what we can try is to re-install the graphics driver, please get into device manager, look for the option "display adapters" then look for "Intel® graphics", right click on it and choose "un-installed". Reverend_Jim, Thank you very much for joining the Intel® graphics communities.