gskinner.com: gBlog: GDispatcher bug fixed.


	Syndication RSS 1.0 RSS 2.0 Subscribe Enter your email address to be notified when posts are added.


	Search


	Resources Conference Session Notes Flash Blogs Waxpraxis Philterblog W3Blog Jonas Galvez Josh Dura Quasimondo Flashguru Sean Voisen Colin Moock Flazoom Greg Burch Pope De Flash Peter Hall Glyn Thomas actionscript.com Princess Pegg Aggregators Flog FullAsAGoog MXNA Hall of Justhese

« [code] GDispatcher: Event swiss army knife. | Back to Main | ClassPath "bug": you should fix this now »

September 30, 2003

IMPORTANT NOTE: This is an old archive. It is only here to support outdated external links. To view the updated version of this archive, please go to the blog index, and search for the title of this document using the search form.

GDispatcher bug fixed.
Posted by Grant

I've uploaded a new version of GDispatcher that fixes a small error in the code that was causing a compiler error.

You can download the new version here (1kb).

There should be a beta 2 release in the next day or so, as I mull through some major compatibility issues with the highly discombobulated UIEventDispatcher class. Some days I wonder if Command HQ doesn't go out of its way to make things overly difficult for us guys in the trenches - the v2 component framework seems to be irrefutable proof of it

Posted @ 03:36 PM by Grant | TrackBack

Comments

Let me know if there's anything I can help with... Not my code, but I guess I know it pretty well.

Posted by: nig at September 30, 2003 05:14 PM

that super.constructor.apply, tip seems to have problems with multiple levels of inheritance. Flash seems to go into 256 levels of recursion if you use it.

Posted by: foo at October 1, 2003 07:06 AM

can gDispatcher be mixed in to replace the eventDispatcher in, for example, UIObject?

I'm trying to make some components (and need them to properly handle parameters) so it looks like I'm pretty much stuck with UIObject for now...see http://chattyfig.figleaf.com/ezmlm/ezmlm-cgi?1:sss:90174#b

I like the approach you're taking with GDispatcher, but need a few of the component authoring hacks that Macromedia wrote for UIObject. Any suggestions?

Posted by: Graphex at October 1, 2003 12:27 PM

Sean - I'm actually working on that right now... there are some major barriers to doing it though (thanks Macromedia), but I should have some kind of solution done later today or tomorrow.

Nigel - email me if you read this.

Cheers,
Grant.

Posted by: Grant Skinner at October 1, 2003 12:33 PM