Skip to content
This repository has been archived by the owner on Apr 26, 2023. It is now read-only.

Capture Method Interface #32

Closed
Avasam opened this issue Jul 12, 2022 · 0 comments
Closed

Capture Method Interface #32

Avasam opened this issue Jul 12, 2022 · 0 comments

Comments

@Avasam
Copy link
Owner

Avasam commented Jul 12, 2022

I'd like to abstract all capture methods behind an interface. This will allow the main logic to be independent of any method's quirks or platform/OS dependency. The interface and all capture methods will go in their own module.

The interface needs to expose:

  • A function to initialize the capture method (some methods need to hook/create/initialize resources).
  • A function to get the current frame. If frame is not ready it should return the previous frame, with an indication as such (so far only the only method that will implement this is device capture. It'll act the same way as WGC API)
  • A function to close the capture method (some methods need to release resources).
  • A function to try and recover the captured window (happens if the captured window was closed, then re-opened)
  • A property is_available to keep platform-specific checks in the capture-method module.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant