recently unify.view.Navigation#navigate was changed to deactivate the current view of all viewmanagers that have none of their views mentioned in the pathfragment argument of navigate.
This is a significant change as it leads to deativation of all but one view if MNavigatable with goto is used or if you use navigate with a small path fragment that contains just one view.
Any application displaying more than one viewmanager side by side (including but not limited to those using splitviewmanager) would have to resort to constantly managing the full path with navigate if it wants to keep active state on all affected viewmanagers.
In my opinion Navigation should not try to keep track of active viewmanagers. Navigations intended purpose is path management, not viewmanager state management.
recently unify.view.Navigation#navigate was changed to deactivate the current view of all viewmanagers that have none of their views mentioned in the pathfragment argument of navigate.
This is a significant change as it leads to deativation of all but one view if MNavigatable with goto is used or if you use navigate with a small path fragment that contains just one view.
Any application displaying more than one viewmanager side by side (including but not limited to those using splitviewmanager) would have to resort to constantly managing the full path with navigate if it wants to keep active state on all affected viewmanagers.
In my opinion Navigation should not try to keep track of active viewmanagers. Navigations intended purpose is path management, not viewmanager state management.