Comments on: No Complete Event for Internal Content https://jessewarden.com/2005/06/no-complete-event-for-internal-content.html Software | Fitness | Gaming Mon, 20 Jun 2005 17:57:53 +0000 hourly 1 By: JesterXL https://jessewarden.com/2005/06/no-complete-event-for-internal-content.html/comment-page-1#comment-2686 Mon, 20 Jun 2005 17:57:53 +0000 http://jessewarden.com/?p=816#comment-2686 Thanks Derek!

mx.core.UIObject & mx.core.ExternalContent do just what you showed; which is a good and solid way to test.

However, Loader is a component, already coded & released in Flash MX 2004 & Flex; hoping it’ll get fixed and/or replaced in the next version of components for both products.

Secondly, Flex abstracts this via binding making you go through a go-between which again points the finger of blame at Loader for being ‘too abstracted’.

]]> By: Derek Vadneau https://jessewarden.com/2005/06/no-complete-event-for-internal-content.html/comment-page-1#comment-2685 Mon, 20 Jun 2005 17:50:28 +0000 http://jessewarden.com/?p=816#comment-2685 Still a bit of a hack, but …
var r = this.attachMovie(resource,’test_mc’,1);
if (r == undefined)
{
// doesn’t exist as resource, must be external.
loaderInstance.loadClip(resource,this);
}

If the resource is internal it will be attached. If the attachMovie fails, the MovieClipLoader method will be called and then events can be handled normally. You could trigger the onLoadComplete if the attachMovie is successful, or extend MovieClipLoader to include this as the new loadClip method.

Just a thought.

]]>