On 6/14/07, Tom Chiverton <[EMAIL PROTECTED]> wrote: > On Thursday 14 Jun 2007, Justin Patrin wrote: > > That is exactly my point. I'm not writing the code. The code causing > > the error is automatically generated by Flex. > > I think you'll have to change the name of your subclass. > I'd expect to see com.foo.YesNo as the base and com.bar.project.CustomYesNo > for instance. >
That's what I ended up doing. It's certainly not something that should be required, though, IMHO, since using the full class name (with package) is perfectly valid code. If Flex 3 hasn't fixed this I'll put in a feature request. -- Justin Patrin
