"Mir simply hides a surface until you've explicitly showed it by calling swapbuffers."
Right. I get that that's how Mir is *supposed* to work. But I'm saying that calling mir::run_mir() in the client calls swap_buffers() four times on the server before even giving control back to the client. So that seems like a bug then, eh? It means that surfaces are shown before there is actual content to show. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280842 Title: [enhancement] Need a method of hiding surfaces until they are ready to draw themselves To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1280842/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
