Renders all the Scenes in the stack, one for each crumb plus the current state. Copied the getScenes from NavigationMotion in mobile because that's its counterpart. Will need the rest of the scene data when it comes to animating on android anyway - can add props to get the animation instead of adding to the state

This reverts commit 9651e0c.

This is for react native 57.8 to match with package.json

Can't call suerp insert because then the react native grumbles that the parent react view controller aren't right. It's expecting the parent to be the host view controller but it's actually the navigation controller. Still need to track the subviews because gonna need them when swipe back and navigate I think because need client and server subviews to match (can't call setState when going back)

Need to think about how to handle back on ios. Need to rerender otherwise if go back and then navigate, React won't think adding a scene, just updating an existing one

Unfortunately it doesn't call removeReactSubview so done something wrong because it means that navigating back from react won't work. Probably do need to insertReactSubview to get the remove called

Otherwise the removeReactSubview isn't called. Without the remove then can't pop viewControllers when navigating back in React. Copied the styling from @jacobp100's NavigatorTest (it's a massive help)

Copied from @jacobp100 NavigatorTest again

This reverts commit 1a36c37.

If the real subview is added then when it's removed during a javascript back navigation the screen goes white when it's popped. Think it's because it's removed from the superview. Adding a placeholder ensures the real superview is retained in teh pop

This works now that inserting a dummy view. It was because the real view was removed from superview that made the screen go blank

When fluently navigated two scenes pushed two scenes but in between the didShow of the first push fired. It looked like a back navigation because the viewControllers < crumbs so it navigated back! Then the second push happened then the setState from the navigateBack which meant it popped the second push!
Applied pushes and pops together after all subview updates which prevents the first push firing the didShow

Changed the name to willAppear to match the ios naming convention. It's a Scene prop now instead of a native event - much better

It's all done through props and components now!

If fluently navigate 2 scenes then still need the title set on the previous scene for the back button text on ios. Have to take this from the navigationEven prop instead of the state

Avoids adding functions to State. The function that was in addNavigateHandler moves to userland
<NavigationStack title={(state, data) => state.getTitle && state.getTitle(data)} />

To simulate slow down a render but putting in a 2 sec sleep.
Then push A,  push B, push C - before C displays press ios back button. Without the locking this would first go back to A (correct) and then display C (wrong) and then go back to A again! That's because the push to C comes back after the ios back. The ios back pop is on the client so happens instantly and then when the C push returns it displays C and then the setState for the pop returns and goes back to A. The locking mechanism is same as in place on TextInput to prevent the typed text and setState(text) getting out of synch

Problem is that removing the SceneView removes all it's children and this makes the Activity go blank as it animates away!!! Overrode removeAllViews of SceneManager so children are kept. Faked the ChildCount of SceneManager to 0 so that React doesn't loop through it's children removing all descendants! This needs revisiting because it prevents the NativeViewHierarchyManager from clearing the Tag arrays. Don't know how to get around this!

Copied this from ReactModalHostView

The SceneManager prevents removal  with fake count and removeAll

Calling finish on current activity no good because the current activity doesn't change between remove calls. So if go back twice it will call finish on the same activity

Tested in current navigation router and it's an existing bug. If you go from A --> B --> C --> D --> E and then navigate back 3 you end up back at D and not B!!! That's because B and D are both SceneActivity with singleTop and so, although it goes back to B it uses the intent from D. I think anyway. It's confusing. I think it reuses the Activity of D at position B!? I guess it makes a bit of sense if navigating forward but navigating back!? Put onNewIntent to read B's crumb and load in B's view after removing D's view!!

if navigate from A --> B --> C --> D --> E and fluently from C to E, then navigate back 3 to B then it will come in the create activity of D because it wasn't created. At that time it will have the crumb for D but there won't be a scene view for it. Still created the host view because onNewIntent is about to run and needs a container

Can get in funny scenarios when reload from dev tools after the error screen. So, clear down activities and start scenes over

It's different than NavigaitonMotion. If going from A--> B  need to work out the enter for B and exit for A but set them both as props on B because B is the only component added. In the addView of stack can read them both

Couldn't read the enter and exit in removeView because it's called before they're set on the current scene!! So moved the start and finish activities into onAfterUpdateTransaction. This is called after views added/removed and props set. But onAfterUpdateTransaction is only called if the props of the NavigationStackView have changed. So forced it to change every navigation by setting url and oldUrl props

Don't make sense on Scene because they relate to two different scenes: the entering one and exiting one

On reload, navigate back to the start activity and clear down the scenes

Otherwise it throws error on reload

Means that double tap R reloads and all the notifications to ReactInstanceManager happen automatically. Not sure why couldn't do this before - maybe because had to destroy react root?!

When a scene's removed trick React Native in thinking it has no children so that it they don't disappear when the scene animates away. The problem with this is that the dropView of NativeViewHierarchyManager doesn't clear it's tag cache for these children. The caches just grow in size when navigating around. So created a SceneBin that says it's children are the discarded scenes  children. That way when the SceneBin is removed from the NavigationStack then these children are dropped and the tag caches cleared! For the SceneBin to be added and removed by updating it's React key whenever 2 seconds have passed between renders

Each navigation stack only had half of the view height. Add another stack and they'd only get a third each! Added stack children to shadow view - trick copied from RCTModalHostViewManager - so they're sized based on whole screen size

Another trick copied from RCTModalHostView. I don't know why it's done with a boundsChange call back to view to resize but safest to copy as is. I guess it's because it doesn't want to pass the bridge around?!

Dropped TabBarItem for now because wasn't doing anything and probably gonna wrap it around stack. TabBar takes tab titles from first screen title anyway

Navigation Stack makes more sense as a child of TabBarItem.  That's how React Native had it when it was part of core https://www.decoide.org/docs/react-native/tabbarios.html

Think it worked before because it ios doesn't use the old scenes. It uses the count and only needs sceneItem for the newly added ones?!

The bounds change handles the resize

Don't need the dummy view insert here because that's only needed to keep the scene children there while animating - prevents early cleanup

The locking mechanism should handle this scenario but the didShowViewController fires late (unlike textChange on TextInput). So it's possible to double tap so fast that didShowViewController doesn't fire for the first tap - which means the nativeEventCoutn doesn't increment and locking mechanism doesn't work. A --> B --> C --> D and tap back 3 times fast. The first back fires didShowViewController and starts a setState. Before it returns the second two taps come in so fast that they don't fire didShowViewController. Then the first setState returns, the counts match and so it wants to do a forward navigation to C - this throws error because C already has a parent view so can't have another

Matches the TabBar definition when it was part of React Native core

When orientation changes it recreates the activity?! But the SceneView can't be added to rootView because it already has a parent. Cleared parent then added to new rootView.
Copied the rest of the DialogRootViewGroup from ReactModalHostView so that the scene resizes when the orientation changes