[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash-commit] gnash ChangeLog server/sprite_instance.cpp serv...
From: |
strk |
Subject: |
Re: [Gnash-commit] gnash ChangeLog server/sprite_instance.cpp serv... |
Date: |
Mon, 2 Apr 2007 11:15:37 +0200 |
On Mon, Apr 02, 2007 at 04:44:22PM +0800, zou lunkai wrote:
> execute_state_reverse() calls execute_state(), and then
> execute_state() calls execute(). so m->add_display_object() is always
> called in execute(). How can we know if add_display_object() is
> called in reverse execution or not if we don't have a another
> variable?
What about adding an execute_state_reversed() to know we're being
executed in "reverse" mode ?
It's still dirty, but moves the dirtiness where it's already dirty
enough :)
--strk;
[Gnash-commit] gnash ChangeLog server/sprite_instance.cpp serv..., Sandro Santilli, 2007/04/06
[Gnash-commit] gnash ChangeLog server/sprite_instance.cpp serv..., Sandro Santilli, 2007/04/10
[Gnash-commit] gnash ChangeLog server/sprite_instance.cpp serv..., Zou Lunkai, 2007/04/15