Skip to content
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

Allow opting out of triggering access dialogs #88

Closed
sindresorhus opened this issue Nov 2, 2020 · 7 comments
Closed

Allow opting out of triggering access dialogs #88

sindresorhus opened this issue Nov 2, 2020 · 7 comments

Comments

@sindresorhus
Copy link
Owner

#67

@wrgoto
Copy link
Contributor

wrgoto commented Jan 18, 2021

This could be really helpful to me. Is it also possible to opt-out of the screen recording permission if we do not need the title? I'm not familiar with Swift, but would be happy to sponsor the change if possible.

@achuinard
Copy link

PR #67 was a good start for this but seems to be abandoned. I (am trying to) use this library in a setInterval and it's totally unusable it its current state.

@wrgoto
Copy link
Contributor

wrgoto commented Jan 27, 2021

@achuinard We use active-win in a setInterval type behavior. Before triggering any interval behavior, it helps to ask for macOS permissions upfront. You might want to take a look at:

https://github.com/karaggeorge/macos-accessibility-permissions
https://github.com/karaggeorge/mac-screen-capture-permissions

I'm going to work on getting something like PR #67 but maybe just limited to the screen recording permissions.

@achuinard
Copy link

I, too, am using setInterval with a simple fork that removes the accessibility check, since I don't need the screen title, just the app name.

@wrgoto
Copy link
Contributor

wrgoto commented Jan 28, 2021

See: #96

@wrgoto
Copy link
Contributor

wrgoto commented Feb 4, 2021

@sindresorhus bump #96

@sindresorhus
Copy link
Owner Author

Done in #177

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants