sbmpost / AutoRaise

AutoRaise (and focus) a window when hovering over it with the mouse
GNU General Public License v3.0
1.42k stars 60 forks source link

Microsoft Teams won't focus #200

Closed pkolano closed 5 months ago

pkolano commented 5 months ago

First off, thanks for a great utility! It makes macs so much more pleasant! I have v5.1 installed with "old_activation_method" and "experimental_focus_first" and use delay=0 to focus without raise. For some reason, all apps I've tried seem to work perfect except microsoft teams. The teams window will not get focus so you have to manually click on it. I noticed that if you use:

ignoreApps="Microsoft Teams (work or school)" invertIgnoreApps=true

the window does get focus so it is capable of automatically getting focus, but for some reason doesn't without those settings. Can you please take a look? Thanks!

sbmpost commented 5 months ago

@pkolano

Are you sure you had been running AutoRaise 5.1 the first time you tried without the workaround? The reason I ask is that if the Microsoft Teams window is excluded by AutoRaise, the logic for your workaround is skipped completely. The workaround therefore shouldn't have solved anything. Additionally, when I start Microsoft Teams on my machine, the main window with the buttons saying "sign-in/join a meeting" focuses correctly. Note that the code deliberately excludes Microsoft Teams "meeting" windows (windows containing actual video) because of the strange behaviour reported in issue #191

pkolano commented 5 months ago

yes, pretty sure I've only ever been using 5.1. It may work ok before you sign in. Microsoft has both "classic" and "new" teams and if you switch between them, there is a window that comes up initially and that window does focus and unfocus just fine. Once you log into the main window, however, and it comes up with the main screen with all your chats, then it starts just ignoring the window. I had looked at that other issue you mentioned, but it seemed to be more about when you have an active meeting going. In my case, I am not in a meeting, but just in the screen where you do most of the interaction with chats, etc. Don't know if there is a way to temporarily disable the special teams handling you fixed in the other issue to see if that may be causing the problem.

sbmpost commented 5 months ago

@pkolano

Don't know if there is a way to temporarily disable the special teams handling you fixed in the other issue to see if that may be causing the problem.

Well, you can start AutoRaise from the commandline with the verbose flag enabled (see the troubleshooting section in the README for more details). Then if you move your mouse over the window that isn't focused, AutoRaise should tell you it is being excluded in the terminal log. It should also tell you the title of that window which is what the exclusion is based on. If you can post that log, then I can hopefully create a fix.

pkolano commented 5 months ago

It shows:

2024-04-08 21:19:26.746 AutoRaise[55281:3116301] Mouse window: Chat | Paul Kolano (You) | Microsoft Teams 2024-04-08 21:19:26.746 AutoRaise[55281:3116301] Excluding window

So I think perhaps the name is completely dynamic. It is showing "Chat" because I was currently in the "Chat" tab of teams (I imagine this might also appear as "Activity", "Teams", "Calls", etc.). It is showing "Paul Kolano (You)" because I was in the "draft chat" area under myself. This could potentially be anything depending on the names of the people/groups in the chat and likely differs depending on which tab you are on. For example, when I switch to "Calendar", it shows as:

2024-04-08 21:25:47.516 AutoRaise[55693:3122650] Mouse window: Calendar | Microsoft Teams 2024-04-08 21:25:47.516 AutoRaise[55693:3122650] Excluding window

Probably the only constant is the "| Microsoft Teams" at the end.

sbmpost commented 5 months ago

| Microsoft Teams

Which is exactly the string filtered on. Given that some people want the filter and others not, it should become a setting instead of being hard coded. It has been on my todo list for a while. If you don't want to wait, a temporary solution could be to downgrade to AutoRaise 4.7. Thanks for the details you have given :-)

sbmpost commented 5 months ago

@pkolano Should be fixed in latest master (AutoRaise v5.2)

pkolano commented 5 months ago

Awesome, thank you! Works perfect now!