-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Give more context on screen recording #31
Comments
Hey! Thanks for your interest! You can take a look at this method here: https://github.com/mandrigin/AlfredSwitchWindows/blob/master/EnumWindows/main.swift#L45 and everything it calls. That’s the Apple presentation about it: https://devstreaming-cdn.apple.com/videos/wwdc/2019/701ngx868rfo8jlj/701/701_advances_in_macos_security.pdf?dl=1 You can search by kCGWindowName that this workflow uses. |
Also, you will need to give the screen recording permission to Alfred, which is more risky than just giving it to |
How I can add it to the Screen Recording Permission list? |
@v-braun on the first use it will ask for this permission. After you install the app, just type |
It is really really strange! |
It looks like these APIs are slower in Catalina. I’m thinking about making windows/tabs enumeration parallel and see how it helps. Instruments show mostly that performSelector is on the hot path. It’s getting a bit annoying because being quick was one of the points of this workflow in the first place. When I have a bit more free time, I will try to experiment a bit more. |
I had once another idea for the same problem: This would end in much better performance and open this awesome tool for much more than a "simple" Alfred Window switching workflow. |
I'm afraid it will have some negative privacy implications. The OS should just handle it faster :) |
... or the OS should handle it faster 😂 |
Hi! Thanks for the project.
Could you please give more context on why screen recording is necessary or when it is used?
I'd love to give this workflow a try but, given that I deal with some sensitive data at work, enabling this permission is a red-flag for me at the moment.
The text was updated successfully, but these errors were encountered: