CameraCaptureUI - API Spec #4721
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pec-draft Update to template format
CameraCaptureUI API Spec
|
/azp run |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
MikeHillberg
approved these changes
Sep 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is API Spec for Issue: #1034
The spec details the implementation of CameraCaptureUI tailored for desktop applications, enabling seamless integration of native camera capture functionalities across Windows platforms supported by WinAppSDK.
The current WinRT CameraCaptureUI, designed primarily for UWP, presents challenges in desktop environments due to dependencies on CoreWindow and lack of IInitializeWithWindow support. Developers resort to complex interop solutions for integration. In response, the CameraCaptureUI API for WinAppSDK provides a streamlined solution with feature parity, now supporting windowID in the constructor for enhanced desktop compatibility.
A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.