NavigationParsley and local scope trouble with waypoints

[MrKoinkoin]

Hi,

I'm using NavigationParsley in order to "switch" three component (using property "automationName") contained in a View A.

This view contains so the waypoint meta tag and a PM (wherever it is) triggers the "switch" by using the  NavigationEvent.createNavigateToEvent(...) event.

This works perfectly on the (default) global scope.

Now I've got the following issue : A tabNavigator having several tabs (same type - I'm using Observer + itemRenderer for the tab) and each of these tabs got their own context.

In the PM which trigger the NavigationEvent (in the specific context)  I'm using the "local" scope to dispatch events. In order to do so my PM contains [ManagedEvents(names="eventName1, eventName2, ..., navigateTo", scope="local")].

I've tested if the NavigationEvent was correctly dispatched by adding in a PM (whithin the same context) the following method:

[MessageHandler(selector="navigateTo",scope="local")]

public function testNavigationEvent(event:NavigationEvent):void{

     trace('test navigation event was caught');

}

And the event is rightly caught (and so dispatched) in the apprpriate context

BUT the view A does not trigger the event based on automationName as it was doing when event was set as "global".

So I guess [Waypoint] in the view A does not handle the event if set as "local" (but then how to set the waypoint as "loacal" ???)

Thx to answer if you get some fix/explanation/everything which could made the Navigatio working with local event

[Alex_Uhlmann]

Agree with you. Can you file a bug?

[MrKoinkoin]

Ok I'm waiting for registration (I thought I've already have one...) and I put the bug in Jira.

[edit]

Ok I've done it : CGM-74

Thx Alex.

Regards,

Cédric

[MrKoinkoin]

Hi,

Any news on this subject ?

Thanks

Cédric

[Alex_Uhlmann]

I will probably not get to work on this in the short term so if it's urgent for you maybe you could try creating a patch for it and attach it to the bug?

[MrKoinkoin]

Hi Alex,

i'm a little bit "stuck" by my project (client's need and not enough time for finding a "good" solution).

For now I've deactivated the use of the Waypoints and only trigger things with event based on selectedIndex (which is not the best design to use...).

So, ok I will wait for a future update and keep my "working but not nice" solution untill then.

[Alex_Uhlmann]

Join the club in being "stuck at projects". Let's keep each other updated once one of us manages to make progress on this in any way. Thanks for your initial workaround.

[MrKoinkoin]

Ok Alex we keep in touch

have a nice day

Cédric