[Top][All Lists]

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

Re: [Gnash-commit] gnash ChangeLog server/as_value.cpp server/as_v...

From: zou lunkai
Subject: Re: [Gnash-commit] gnash ChangeLog server/as_value.cpp server/as_v...
Date: Tue, 27 Nov 2007 09:02:29 +0800

On Nov 27, 2007 8:53 AM, zou lunkai <address@hidden> wrote:
> +       /// @param allowUnloaded
> +       ///     If true an unloaded sprite is still returned as such,
> +       ///     rather then attempted to be resolved as a soft-reference.
> +       ///     Main use for this is during paths resolution, to avoid
> +       ///     infinite loops. See bug #21647.
> +       ///
> +       sprite_instance* to_sprite(bool allowUnloaded=false) const;
> In which scenario we are not allowed to access an unloaded sprites?
> Shouldn't  to_sprite() always allow unloaded characters?

In ActionScript level,  unloaded(but not destroyed) characters are
always accessible by both hard references an soft  references. So
to_sprite(bool allowUnloaded=false) is bit of confusing,  isn't it?


reply via email to

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