You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using a state machine in a Navigator seemed one of the main advantages of using these Navigators when beginning to design the library. In practice actually, using state machines may prove to be more difficult than initially thought -- there's Scene management, View hierarchy saving, Scene state saving, etc. Combining these with a state machine is not that trivial at all.
Especially with the power that comes with the composing of Navigators, state machines become less necessary. There are definitely cases where state machines may be a better choice, but before that happens some more thought in how to actually implement Navigators with them is necessary.
The text was updated successfully, but these errors were encountered:
Using a state machine in a Navigator seemed one of the main advantages of using these Navigators when beginning to design the library. In practice actually, using state machines may prove to be more difficult than initially thought -- there's Scene management, View hierarchy saving, Scene state saving, etc. Combining these with a state machine is not that trivial at all.
Especially with the power that comes with the composing of Navigators, state machines become less necessary. There are definitely cases where state machines may be a better choice, but before that happens some more thought in how to actually implement Navigators with them is necessary.
The text was updated successfully, but these errors were encountered: