Re: [flexcoders] flex2 - ambiguous reference to TextInput

Thu, 04 May 2006 04:55:40 -0700

Hi,

You could also do;

public class Textnput extends mx.controls.TextInput

I agree with Manish, I am creating a large set of components and experiemented with using base names like that. I swear now after a couple months it is not worth it.

Just come up witha a 1-3 letter acronym or something to signifiy this is one of 'your' published components. It works well and if people have to type 2 more letters for clarity and null name collisions, well whatever ;-)

Peace, Mike

On 5/4/06, Manish Jethani <[EMAIL PROTECTED]> wrote:
On 5/4/06, bhaq1972 <[EMAIL PROTECTED]> wrote:
> I created my own extended TextInput control which i have named
> TextInput.mxml.
>
> but i'm getting a compiler error
>
> "Ambiguous reference to TextInput. [CODEGEN C:\Documents and
> Settings.......\mycontrols\TextInput.mxml"

It might be because the compiler's generated code looks like this:

import mx.controls.TextInput;

public class Textnput extends TextInput /* note: name not fully-qualified */

Should probably fixed in the compiler. For now, use a different name.
(In general it's a good idea not to use "reserved" names.)



--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com



SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS





--
What goes up, does come down.

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com



SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice

YAHOO! GROUPS LINKS



Reply via email to