| commit | 89653d5db46419d2a80898635cb27fed64898db2 | [log] [tgz] |
|---|---|---|
| author | braveyao <braveyao@webrtc.org> | Tue May 15 15:52:17 2018 -0700 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed May 16 16:44:01 2018 +0000 |
| tree | 3a525a049ca12c30db8044dd3d5ccd7b457fa27c | |
| parent | a8bf169906beacdf5520d6fbe47498e7b7e971a6 [diff] |
[desktopCapture] Unify the position info in DIP coordinates on Mac. On OSX, the logical(DIP) and physical coordinates are used mixingly. For example, the captured image has its size in physical pixels(2x) and location in logical(DIP) pixels. Same to the cursor position. This causes trouble when we check the relative position of image and cursor when there are multiple monitors with different DIP setting connected. This cl proposed a solution to use DIP pixel for any location info, i.e. top-left of a frame and cursor position. Also propose a method to get the current scale factor of a window across multiple monitors. And save the current scale factor in DPI of the capture frame. Then we can check relative position of cursor and frame correctly in DIP pixel and compose them in physical pixel. Bug: webrtc:9178 Change-Id: I3c076aeac2d6f2c1f63d000d7fff03500aa375ac Reviewed-on: https://webrtc-review.googlesource.com/71621 Reviewed-by: Jamie Walch <jamiewalch@chromium.org> Reviewed-by: Zijie He <zijiehe@chromium.org> Commit-Queue: Brave Yao <braveyao@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23263}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.