** Changed in: nux
Importance: Undecided => High
** Also affects: nux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nux (Ubuntu)
Status: New => In Progress
** Changed in: nux (Ubuntu)
Importance: Undecided => High
** Changed in: nux (Ubuntu)
Assignee: (unassigned) => Sam Spilsbury (smspillaz)
** Branch linked: lp:~unity-team/nux/nux.fix_1091589.1
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to nux in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1091589
Title:
Nux draws every single BaseWindow to the backbuffer regardless of what
the host WM draw region is
Status in Nux:
In Progress
Status in “nux” package in Ubuntu:
In Progress
Bug description:
At the moment, this bug is essentially the reason why bug 1091583
exists in unity.
When we switched to using backbuffer persistence in compiz, it means
that it was no longer permissible for plugins to draw outside damage
boundaries, as that would result in bleeding from the regions beneath
not being redrawn. At the moment, calling
nux::WindowThread::RenderInterfaceFromForeignCmd causes the entire
interface to be drawn on-screen, regardless of the damage region
inside of compiz. This means bleeding everywhere.
Nux should support the concept of being able to selectively present
its render targets to the screen, so that there's no overdraw when we
only need to re-present, eg, the launcher or the panel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1091589/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
