commit | c58a767a23ab620a78fd92aa9d869881ba8afd25 | [log] [tgz] |
---|---|---|
author | Palak Agarwal <agpalak@google.com> | Fri Jan 31 12:56:30 2025 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 31 14:36:04 2025 |
tree | 9aa06ca23f8e9f91b6fe8c6784056c62c2471865 | |
parent | 18b94b517d808bfaf8ba1559c45de61b403ff52a [diff] |
Reland "Get DeviceScaleFactor for the captured monitor/screen" This is a reland of commit e20fbb00d0e0219b710da24664e81a10b12c703a which failed due to CHECK failing on monitor_id in DxgiDuplicatorController::GetDeviceScaleFactor(). This has now been fixed in this CL by removing the check for greater than 0 and instead returning std::nullopt. Original change's description: > Get DeviceScaleFactor for the captured monitor/screen > > Accesses DeviceScaleFactor using the windows API > GetScaleFactorForMonitor and adds it to the DesktopFrame. In a follow-up > CL, this value is propagated to > DesktopCaptureDevice::Core::OnCaptureResult where it is added to the > frame metadata. > > In a follow-up CL, add RegisterScaleChangeEvent to get notified whenever > the device scale factor changes. > > Design doc: go/expose-captured-surface-resolution > > Bug: chromium:383946052 > Change-Id: I363af33c569419d95ddf31a0cc2f9cecf6fb0c7b > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/374344 > Reviewed-by: Henrik Andreassson <henrika@webrtc.org> > Reviewed-by: Mark Foltz <mfoltz@chromium.org> > Commit-Queue: Palak Agarwal <agpalak@google.com> > Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#43827} Bug: chromium:383946052 Change-Id: Iffcc889b9a560695302f71623e3e929ecb2489fb Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/376061 Commit-Queue: Palak Agarwal <agpalak@google.com> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Henrik Andreassson <henrika@webrtc.org> Cr-Commit-Position: refs/heads/main@{#43832}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.