Hi Oriol,
 
There is still a selectedChild property on ViewStack. The only thing you need to do is type stronger. UIComponent is the base class of Container but Containter goes into a ViewStack. Beta 2 is stricter here.
 
In addition to that, I wouldn't recommend your workaround using the Number in the workflow state variable. As soon as you'll add another workflow type variable to ModelLocator, you would need new state variable values, which could not map to ViewStack::selectedIndex anymore.
 
Best,
Alex
 
Alex Uhlmann
Consultant (Rich Internet Applications)
Adobe Consulting
Westpoint, 4 Redheughs Rigg, South Gyle, Edinburgh, EH12 9DQ, UK
p: +44 (0) 131 338 6969
m: +44 (0) 7917 428 951 
[EMAIL PROTECTED]

 


From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Oriol Gual
Sent: 21 March 2006 20:16
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Cairgnorm beta release?

Just one more point, I've tried the Cairngorm login example, and after changing the namespaces to http://www.adobe.com/2006/mxml, I can compile but I get this error:

Implicit coercion of a value with static type ' mx.core:UIComponent' to a possibly unrelated type 'mx.core:Container' in line 68, which is:

<mx:ViewStack id="appView" selectedChild="{ getView( model.workflowState ) }">

If look at it, and viewstack has no selectedChild propertie, so if I change it to: selectedIndex="{ model.workflowState }" it works. My question is, how should it be if I want to return a view instead of an int?

Thanks,

Oriol.


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




YAHOO! GROUPS LINKS




Reply via email to