Ooops... I tried a clean build and it worked. Adding the [Bindable] tag to the interface made the warning go away!
So thanks a lot Josh and Alex! :) I am now wondering, like Ralf, what are the implications of making the interface bindable... Does it mean that when one property changes all watchers are getting called (like a bindable calss)? How will this affect the implementing class behavior? Sefi On Wed, Aug 27, 2008 at 9:41 AM, Sefi Ninio <[EMAIL PROTECTED]> wrote: > I tried to add the [Bindable] tag to the interface, but that did not make > the compile-time warning go away... > > > On Wed, Aug 27, 2008 at 9:36 AM, Josh McDonald <[EMAIL PROTECTED]> wrote: > >> I hope not :) >> >> On Wed, Aug 27, 2008 at 4:31 PM, Ralf Bokelberg <[EMAIL PROTECTED] >> > wrote: >> >>> I wonder, what happens, if you make a interface bindable. Does this >>> change the code beeing created from the implementing class? >>> >>> Cheers >>> Ralf. >>> >>> On Wed, Aug 27, 2008 at 8:22 AM, Josh McDonald <[EMAIL PROTECTED]> wrote: >>> > I thought he was talking about a compile-time warning :) >>> > >>> > On Wed, Aug 27, 2008 at 3:40 PM, Alex Harui <[EMAIL PROTECTED]> wrote: >>> >> >>> >> The final class that gets listened to needs to have its property be >>> >> bindable. The interface being bindable gets you past the compiler, >>> but the >>> >> warning is a run-time when it actually looks at the instance it is >>> hooking >>> >> up to. >>> >> >>> >>> ------------------------------------ >>> >>> -- >>> Flexcoders Mailing List >>> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt >>> Search Archives: >>> http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups >>> Links >>> >>> >>> >>> >> >> >> -- >> "Therefore, send not to know For whom the bell tolls. It tolls for thee." >> >> :: Josh 'G-Funk' McDonald >> :: 0437 221 380 :: [EMAIL PROTECTED] >> >> > >
