Best practice for Request-Screen-Orientation-Change? about mortar

[creativepsyco]

Thats coz the traversal hasn't completed for the new screen and screen orientation causes the activity to be recreated, which makes the old history be restored. You can try to make the newer history be stored and let the orientation dictate the dispatching:

• Hook into the onTraversalCompleted callback in your dispatcher to invoke any necessary orientation changes after the traversal completes, i.e. queue it up
• Short-circuit the traversal (call onTraversalCompleted) if there is a orientation change required and let the orientation change construct the screen with the new history.
• Instead of doing a delay post just posting on the UI thread suffices.

[rjrjr]

square/flow#204