Thanks!
--- In [email protected], "Alex Harui" <[EMAIL PROTECTED]> wrote:
>
> At startup, the image is created so creationComplete fired and
> updateComplete also fires since that means the image has finished
> updating, but the image has no bits yet, they are still streaming in,
> kiadin external data is asynch, later, a "complete" event will be
> dispatched which means the bits are stremed in, and the image will
> adjust, causing another updateComplete. There is no reason to use
> creationComplete in this scenario
>
