Nested server needs full control over cursor position

Last time we discussed this I suggested the Mir client API just needed something like mir_warp_cursor_to(x, y) [where x,y might be relative to a surface, which might be a fullscreen Unity8 surface]. And you could limit the operation to the currently focussed surface too, so there are no privilege concerns.

Since Unity8 is just a client of USC I feel like that should resolve this...?

And the cursor would only move in response to mir_warp_cursor_to(x, y) calls when in such mode?

I'm sure that there are multiple discussions about controlling the cursor from a nested server. These ought to be collated to ensure we have an overview of all the requirements before implementing piecemeal solutions.

It's more complicated than I thought, as I forgot we need to pass through cursor bitmaps, buffer streams and hotspot information. This bug isn't really about just a position.

Also anpok is already working on it...

Status changed to 'Confirmed' because the bug affects multiple users.

Syncing task from Mir.