AFAIK all it's telling you is that Flex won't be able to auto-detect
changes to that property in testModel and automatically notify your
component.
If you change the whole model by reassigning the testModel variable,
your component will be notified.
It doesn't actually affect the workings of the UI in a lot of cases and
you may want to do it this way. I think the warning on first compile is
there to make sure you're aware that's what will happen.
Have you tried declaring the testModel with ActionScript rather than an
mx:Model tag?
Spike
Scott Barnes wrote:
> I have a really weird situation here, basically i have:
>
> --index.mxml---
>
> <mx:Model id="testModel">
> <firstName>Scott</firstName>
> </mx:Model>
>
>
> <inco:dspTravelProfile employeeModel="{this.testModel}" />
>
> -- dspTravelProfile.mxml--
> <mx:Script>
> <![CDATA]
> public var employeeModel;
> ]]>
> </mx:Script>
>
> <mx:FormItem label="First Name:">
> <mx:Label text="{employeeModel.firstName}"/>
> </mx:FormItem>
>
> When I first save/change the physical mxml and then run, i get this
> message in the compiler:
>
> "Changes to unknown property, firstName will not be detected."
>
> -THEN-
>
> I hit refresh again, and it goes away? Is this just a polite
> exception? and how do you pass down a byReference as a variable into
> other components? (if its possible)
>
--
--------------------------------------------
Stephen Milligan
Code poet for hire
http://www.spike.org.uk
Do you cfeclipse? http://cfeclipse.tigris.org
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
