Also note the current window resizing implementation in QtMir is creating additional lag that shouldn't be there. Waiting for the client to update simply takes too long. As a result, the window edges lag behind the mouse cursor. However since Unity8 renders its own mouse cursor there should be _zero_ visible lag between the cursor and the screen, as demonstrated with:
Also note the current window resizing implementation in QtMir is creating additional lag that shouldn't be there. Waiting for the client to update simply takes too long. As a result, the window edges lag behind the mouse cursor. However since Unity8 renders its own mouse cursor there should be _zero_ visible lag between the cursor and the screen, as demonstrated with:
mir_demo_ client_ target -m /var/run/ user/1000/ mir_socket -- --desktop_ file_hint= unity8
(after you resize it... seems there's a new QtMir bug there)