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 :) Or is it isMaskLayer() that's going the opposite direction? Sorry, haven't the code at hand.. SS> We'd know from the start wheter we're calling ::display because we're SS> rendering a character as mask or not. ...to avoid isMaskLayer(), ie. just for the visibility fixes? Odd, but would make sense. SS> It's already implemented, is the original mail in this thread :) Nice! :) Udo _______________________________________________ Gnash-commit mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-commit
