Others have already addressed your specific question.
However, if you want a "portable" component, the best solution is for
t he login component to broadcast an event, and your main application to
listen for it and change the state.
Chad Gray wrote:
>
>
> Say I have a component file that is called Login. It asks for login and
> password and if they succeed I want the currentState of the main MXML
> file to change to one called "main".
>
> When I had all of the code on the one main mxml I used this code to
> change the state:
>
> private function letUserIn():void{
> if (roServalent.authUser.lastResult == true) {
> this.currentState = 'main';
> }
> }
>
> When I run this code in the component file I get an error
> "ArgumentError: Undefined state 'main'."
>
> I know the scope "this.currentState" is what is causing the error.
>
> How do I scope currentState so it can find the "main" state in the main
> MXML file?
>
> I guessed super.currentState but that did not seem to work.
--
Jeffry Houser
Flex, ColdFusion, AIR
AIM: Reboog711 | Phone: 1-203-379-0773
--
Adobe Community Expert
<http://www.adobe.com/communities/experts/members/JeffryHouser.html>
My Company: <http://www.dot-com-it.com>
My Podcast: <http://www.theflexshow.com>
My Blog: <http://www.jeffryhouser.com>
