Though, the Unity code doesn't seem to use HSplitter or VSplitter. Also,
it doesn't call QueueRelayout on any InputArea objects, which seems to
be the only other way for an InputArea object to be put on the layout
queue. Btw the parent object of an object of type InputArea is a Layout
object
It seems like FloatingWindow is being added to the queue with
QueueObjectLayout in FloatingWindow.cpp, but might not be removed from
the queue before it's deleted. Its ancestor Area has the same potential
issue, as well. So, moving the RemoveObjectFromLayoutQueue call in View
and Layout
** Patch removed: nux-remove-area-from-layout-queue.patch
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1337244/+attachment/4164791/+files/nux-remove-area-from-layout-queue.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
However, if the parent object of an object of type InputArea is a
Layout object comment at Area.cpp:603 is inaccurate (as some of the
other comments there, such as the ones at :540, :576, and :596), and if
InputArea objects can have HSplitter or VSplitter as parent, then they
could be added to the
And since InputArea and Layout are the only classes derived directly
from Area, and they would both have the same code in their destructors
with the patch in #6, the removal code can be moved to the Area
destructor, as in the attached patch.
** Patch added: nux-remove-area-from-layout-queue.patch
5 matches
Mail list logo
