Code review comment for lp:~kdub/mir/fix-1597717

> I assume that there's some godawful Qt-ish reason why we're doing this rather
> than just throwing an exception if the shell tries to set a 0x0 cursor and
> then fixing QtMir?
>
> Assuming there is such a reason, +1.

Right, it appears that they want to disable us showing our cursor, as well as set a Qt-specific cursor name for their renderer to use.