Skip to content

Conversation

@lrettig
Copy link
Owner

@lrettig lrettig commented Mar 7, 2016

No description provided.

JackWink and others added 27 commits February 24, 2016 21:34
always use hideNavBar in example instead showNavigationBar to avoid confusion
Fix pop handling for multi-pop situations
use hideNavBar in example. close #262
Pass updated props to an existing route
follow up #270
always use hideNavBar in example instead showNavigationBar to avoid confusion
use hideNavBar in README example
The NoTransition scene config produces an interpolator function with a
divide by zero, which can cause scenes to have opacity=NaN when
directionAdjustedProgress is set to 1.

This bad value is interpreted on Simulator as opacity=1 (bug does not
appear) but on my device it shows up as opacity=0 (scene shows briefly and
then disappears).

The 'constant' type seems more appropriate here.
NoTransition scene config causes blank scenes
Fixes crash when currentRouter is already null.
ExRouter add onTransitionToTop , like ExNavigator transitionToTop ,  …
Added missing defaultRoute action to tabbar
Check if current router exists
When invoking Actions.refresh({title: 'Changed'}), the call to
super.render() in ExNavigationBar calls back into getTitle() on
ExRouteAdapter to determine the title to display in the navigation bar
This patch first checks the provided props before falling back to the
previous behavior.
Use route props first when determining route title
upgrade examples to React Native 0.20.0
lrettig added a commit that referenced this pull request Mar 7, 2016
@lrettig lrettig merged commit 686702d into lrettig:master Mar 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants