[Chromoting] Fix display selection on windows host
This moves the display scanning code to always be in the DesktopCapturerProxy (DCP). Previously, it was located in the DesktopSessionAgent (DSA) for Windows and in the DCP for Mac. The change to record the display id along with the geometry info broke Windows because that info was calculated in the DSA, but not available in the DCP. By moving all the display scanning into the DCP, this problem is fixed. This also removes the duplicate code and increases the likelihood that it2me will "just work". This works because, on Windows Me2me, the DSA serves as the ClientSessionController, and passes the message across the process boundary to the real ClientSessionController. Bug: 915411 Change-Id: Iecdd827b82c5e75e4a493f31cc31a6555388d4ca Reviewed-on: https://chromium-review.googlesource.com/c/1485016Reviewed-by:Joe Downing <joedow@chromium.org> Commit-Queue: Gary Kacmarcik <garykac@chromium.org> Cr-Commit-Position: refs/heads/master@{#635183}
Showing
Please register or sign in to comment