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

Improve Screenshots/ViewHierarchy mechanism #2713

Closed
markushi opened this issue May 17, 2023 · 0 comments · Fixed by #2773
Closed

Improve Screenshots/ViewHierarchy mechanism #2713

markushi opened this issue May 17, 2023 · 0 comments · Fixed by #2773

Comments

@markushi
Copy link
Member

Problem Statement

Right now there's little control over capturing Screenshots/VH. This can have a negative impact on the app performance itself (capturing many screenshots, contribution to quota) as well as the usability of the feature itself (no control when a screenshot should be taken or not).

Solution Brainstorm

  • Add debouncing mechansim
    Capturing many subsequent screenshots may has a negative performance impact (both CPU and memory).

  • Introduce BeforeCaptureScreenshotCalback/BeforeCaptureViewHierarchyCallback
    We want to provide more controls over when and what events for a screenshot should be taken. Thus providing a hook before the screenshot is taken makes most sense here.

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

Successfully merging a pull request may close this issue.

1 participant