ozone: dri: Support moving between displays in MoveCursorTo(location)

ozone: dri: Support moving between displays in MoveCursorTo(location)

Let's use screen location for this API, to allow moving the cursor to
any allowed location.

If we do that, we need a way to find a window containing a screen point,
so add that to DriWindowManager.

TEST=unit tests
BUG=437035
Committed: https://crrev.com/0dcb1bebd150593a52bfa47883d32465de20d594
Cr-Commit-Position: refs/heads/master@{#306026}

[spang, 2014-11-27 00:40:59]

spang@chromium.org changed reviewers:
+ dnicoara@chromium.org

[dnicoara, 2014-11-27 15:48:32]

I think I understand the overall changes in your patch series. But just want to
double check: the intent is to have events reported in screen location to
simplify targeting. The part that I'm fuzzy on is the "moving between displays".
I am worried that you'll be able to move the cursor to another display due to
the MoveCursorTo(location) method. This would be wrong right now since Ozone
doesn't have the true display layout.

[spang, 2014-11-27 18:09:11]

On 2014/11/27 15:48:32, dnicoara wrote:
> I think I understand the overall changes in your patch series. But just want
to
> double check: the intent is to have events reported in screen location to
> simplify targeting. The part that I'm fuzzy on is the "moving between
displays".
> I am worried that you'll be able to move the cursor to another display due to
> the MoveCursorTo(location) method. This would be wrong right now since Ozone
> doesn't have the true display layout.

Why wrong? Either

WindowTreeHost* host;
host->MoveCursorTo(location)

or

WindowTreeHost* host;
host->ConvertPointToNativeScreen(&location);

SystemInputInjector* injector;
injector->MoveCursorTo(location);

are actually asking to move it between displays and doing so correctly even with
the crazy transforms.

The injector and tablet thing are the only callers of this, and remoting doesn't
even support multi-display. If it did, this is how it would need to work anyway.

[dnicoara, 2014-11-27 18:28:31]

lgtm

Ahh, my bad, my mental stack trace broke.

[spang, 2014-11-27 20:23:15]

The CQ bit was checked by spang@chromium.org

[commit-bot: I haz the power, 2014-11-27 20:24:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/766583002/1

[commit-bot: I haz the power, 2014-11-27 21:03:22]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-11-27 21:04:03]

Patchset 1 (id:??) landed as
https://crrev.com/0dcb1bebd150593a52bfa47883d32465de20d594
Cr-Commit-Position: refs/heads/master@{#306026}