Also, I think we should not be supporting or encouraging client-drawn shadows. They do create the edge placement extents problem mentioned in the description, but also result in an inconsistent look to the overall desktop. I think even if a client provides its own "decoration", that should not include shadows. The shell should be in charge of shadows so that they all appear consistent and seamless (if present at all).
As for what to do about odd-shaped surfaces with an alpha channel, I know generating a shadow for those is not efficient and needs to not be recalculated on every frame. I suggest that following the surface's input region shape is best there, or to add a client function to notify the server of shape changes (roll it in with resizing?). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1398849 Title: support client-side window decorations (GTK on Mir) Status in Mir: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Bug description: I can't find a way for telling Mir that we have decorations drawn client-side and the result is that we have two sets of decorations (and shadows) when running Gtk applications under the demo server. It would be nice if we could tell the display server that we are drawing the decorations. Also up for discussion: if the client is going to be drawing the shadows then we also need a "frame extents" sort of mechanism that we can use to tell Mir how large the shadows are. This needs to be compensated for when performing various window management tasks (eg: snap to edge). To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1398849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
