Problem with the navigation library with states in modules

[After24]

Hello,

The application I'm working on is based on a shell which contain a "contentNavigator" where several states are defined :

<code>

...

<fx:Declarations>

        <parsley:Configure />

    </fx:Declarations>

    <fx:Metadata>

        [Waypoint(mode="states",name="shell")]

    </fx:Metadata>

    <s:states>

        <s:State name="dashboardModule" />

        <s:State name="registrationModule" />

        <s:State name="marketingModule" />

        ...       

    </s:states>

    <components:ModulePad id="dashboard" includeIn="dashboardModule"  url="../../dashboard/bin-debug/dashboardModule.swf" />

    <components:ModulePad id="registration" includeIn="registrationModule"  url="../../registration/bin-debug/registrationModule.swf" />

    ... 

</code>

Each ModulePad is a custom component that manage the loading/unloading of a spark module. The navigation in each spark module is based on the same principle, for example in the registrationModule :

<code>

...

    <fx:Declarations>

        <parsley:ContextBuilder config="RegistrationContext" />

        <parsley:Configure />

    </fx:Declarations>

    <fx:Metadata>

        [Waypoint(mode="states",name="shell.registrationModule")]

    </fx:Metadata>

    <s:states>

        <s:State name="registration" />

        <s:State name="tracking" />

    </s:states>

    <presentation:Registration includeIn="registration" width="1000" top="130" left="40" bottom="30"/>

    <presentation:RegistrationTracking includeIn="tracking" width="1000" top="130" left="40" bottom="30"/>

    ...

</code>

At the beginning the navigation is working properly : when a NavigationEvent ("shell.registrationModule.tracking") is dispatched the registrationModule is loaded and when the loading is done the state is set to "tracking".

Then if a NavigationEvent ("shell.dashboardModule.dashboard") is dispatched the registrationModule is automatically unloaded and the dashboardModule is loaded. But then if a NavigationEvent ("shell.registrationModule.tracking") is dispatched again, the state is set to "registration" (the default one) instead of "tracking" like the first time.

The event log show that a (com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.tracking:exit) is triggered just after the load of the registrationModule.

Is this a bug or am i making a mistake in the implementation of the navigation ?

Thanks for you help.

[After24]

Here is the log of the navigation events if it can help :

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell:firstEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell:everyEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher waypointChange shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule:firstEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule:everyEnter

[SWF] Users:vincentjuge:Documents:Adobe Flash Builder 4.5:ThalamusDashboard:bin-debug:DashboardModule.swf - 1 052 130 octets après la décompression

com.adobe.cairngorm.navigation.core.NavigationDispatcher waypointChange shell.dashboardModule

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule.dashboard:firstEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule.dashboard:everyEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule.dashboard:exit

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule:exit

com.adobe.cairngorm.navigation.core.NavigationDispatcher waypointChange shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule:firstEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule:everyEnter

[SWF] Users:vincentjuge:Documents:Adobe Flash Builder 4.5:ThalamusRegistration:bin-debug:RegistrationModule.swf - 1 108 823 octets après la décompression

com.adobe.cairngorm.navigation.core.NavigationDispatcher waypointChange shell.registrationModule

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.tracking:firstEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.tracking:everyEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.tracking:exit

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule:exit

com.adobe.cairngorm.navigation.core.NavigationDispatcher waypointChange shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule.dashboard:enter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule.dashboard:everyEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule:enter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule:everyEnter

[SWF] Users:vincentjuge:Documents:Adobe Flash Builder 4.5:ThalamusDashboard:bin-debug:DashboardModule.swf - 1 052 130 octets après la décompression

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule.dashboard:exit

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.dashboardModule:exit

com.adobe.cairngorm.navigation.core.NavigationDispatcher waypointChange shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.tracking:enter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.tracking:everyEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule:enter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule:everyEnter

[SWF] Users:vincentjuge:Documents:Adobe Flash Builder 4.5:ThalamusRegistration:bin-debug:RegistrationModule.swf - 1 108 823 octets après la décompression

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.tracking:exit

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.registration:firstEnter

com.adobe.cairngorm.navigation.core.NavigationDispatcher shell.registrationModule.registration:everyEnter

[Décharger SWF] Users:vincentjuge:Documents:Adobe Flash Builder 4.5:ThalamusDashboard:bin-debug:DashboardModule.swf

[Décharger SWF] Users:vincentjuge:Documents:Adobe Flash Builder 4.5:Thalamus:bin-debug:Thalamus.swf

[SDonerza]

As I said, this forum looks dead, there's no one to reply.

Now that Adobe's gonna cut 1000 jobs all over the world, no one knows what this forum will become.

[After24]

Anyone ?

This is the second time I try to use a Cairgornm 3 library and for the second time I'm experiencing some problems with it. Having some issues is common in the development process but in this particular case I'm a bit upset against Adobe and his Cairngorm thing :

I'm definitely not a flex guru but I try  to improve the architecture and the code of the applications I'm working on every day. The fact that Adobe provides recommandations, guidelines and libraries to reach that goal is great but I think that an essential thing is missing in the case of Cairngorm : SUPPORT.

Librairies :

- Documentation is minimalist

- Sample applications are not regularly updated nor well commented so learning to use them isn't a no brainer (at least for me)

Dedicated forum :

- The cairngorm development forum seems to be dead. What is the purpose of maintaining a forum in which it is very unlikely to find answers?

If someone at Adobe read this post, a response would be much appreciated even if it is something like :

- Your question is so dumb that I don't want to spend time on it

- Sorry but the one who was in charge is one of the 750 to be fired

- Please contact Adobe Consulting if you need answers

Sorry to be a bit upset but I have spent about 4 days on the Module and navigation libraries to get to the conclusion that it's not working in my use case although I can't find out if the problem comes from the libraries or from the way I use them.