« Hide

(This is a little complicated so please bear with me.)

Steps to reproduce:
1. Create an interface Foo that extends an interface (e.g., IEventDispatcher, because objects of this type must be able able to dispatch events to listeners)
2. Create a class Bar that implements Foo and extends a class (e.g., EventDispatcher) that also implements the interface that Foo extends
 
 Actual Results:
 The class creation wizard just adds all the unnecssary methods from IEventDispatcher and then the editor shows 1024 errors (overriding methods without marking for override)

 Expected Results:
 The class creation wizard should check all the methods that are *already* in place, by extending the class (e.g., addEventListener has been inherited from EventDispatcher) and any of the same methods in the interface should be ignored.
 
 Workaround (if any):
 You can just delete the methods. But it makes Flex Builder look like it's malfunctioning. You shouldn't get errors from code produced automatically.
 
Note:
You might ask, isn't it redundant for the developer to be implementing IEventDispatcher if s/he is also extending EventDispatcher? Think again. Our class Bar does not directly implement IEventDispatcher. It implements Foo. So the relationship is indirect. I need Foo to inherit from IEventDispatcher so that I can later deal with objects of type Foo without ever needing what actual class has implemented Foo.

Show »

(This is a little complicated so please bear with me.) Steps to reproduce: 1. Create an interface Foo that extends an interface (e.g., IEventDispatcher, because objects of this type must be able able to dispatch events to listeners) 2. Create a class Bar that implements Foo and extends a class (e.g., EventDispatcher) that also implements the interface that Foo extends    Actual Results:  The class creation wizard just adds all the unnecssary methods from IEventDispatcher and then the editor shows 1024 errors (overriding methods without marking for override)  Expected Results:  The class creation wizard should check all the methods that are *already* in place, by extending the class (e.g., addEventListener has been inherited from EventDispatcher) and any of the same methods in the interface should be ignored.    Workaround (if any):  You can just delete the methods. But it makes Flex Builder look like it's malfunctioning. You shouldn't get errors from code produced automatically.   Note: You might ask, isn't it redundant for the developer to be implementing IEventDispatcher if s/he is also extending EventDispatcher? Think again. Our class Bar does not directly implement IEventDispatcher. It implements Foo. So the relationship is indirect. I need Foo to inherit from IEventDispatcher so that I can later deal with objects of type Foo without ever needing what actual class has implemented Foo.