gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash ChangeLog server/character.h server/dlist...


From: Sandro Santilli
Subject: Re: [Gnash-commit] gnash ChangeLog server/character.h server/dlist...
Date: Tue, 30 Oct 2007 17:29:15 +0100

On Tue, Oct 30, 2007 at 05:12:41PM +0100, Udo Giacomozzi wrote:
> Hello Sandro,
> 
> Tuesday, October 30, 2007, 3:00:23 PM, you wrote:
> SS> Yes, it's the parent's scan.
> SS> If we had two distinct functions (or an additional argument to
> SS> display) we shouldn't need to do that scan, right ?
> 
> We don't do any special scan, we're just following the hierarchy and
> remembering mask state :)

we're following the hierarchy of any component of the DisplayList.
Consider a long long hierarchy ending with a big park of childs.
For each of the elements in the park:

                bool renderAsMask = ch->isMaskLayer();
                while(!renderAsMask && parent)
                {
                    renderAsMask = parent->isMaskLayer();
                    parent = parent->get_parent();
                }

All the characters share the same parent, btw, so the parent's
scan isn't really needed to replicate for *each* character.
There could be an hineritance scan outside the loop for example.
(less painful change)

--strk;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]