I have a YesNo class in the com.example.element package which
implements a generic YesNo component. I then have a YesNo class in the
com.example.product.element package which has package specific code.
This works just fine if I am not using bindings. However, if I use a
{} binding in the MXML of the package YesNo I get a generated code
error saying that the usage of class YesNo is ambiguous.

It looks like the code generator is incorrectly assuming that all
classes used will have different names and importing the generic
YesNo, causing this error.

Any easy fix would be to include the package in the class use I would think.

Anyone know a workaround which does not involve changing the name of
the extended class?

-- 
Justin Patrin

Reply via email to