Create model that is not in main about scoped_model HOT 3 CLOSED

If you want to share the model across different Screens in your app, the ScopedModel will need to wrap the MaterialApp or WidgetsApp. This is because the MaterialApp creates all screens when you use Navigator.push etc, and therefore the ScopedModel needs to be a parent of all screens.

If you only want to use the Model on a Single screen, you can create it in the Root Widget of a Screen (e.g. Home.dart) and all children of that Widget will have access to the ScopedModel.

If you don't want to create the Model until you log in, your MyApp Widget which creates the MaterialApp could be a stateful widget. When the login occurs, you could do a setState on the MyApp widget with some information about the login and then wrap the MaterialApp with a scoped model on rebuild if the data exists.

Another way to approach this problem: Create your ScopedModel when the app starts, and use it to drive the login process. This means: When the user logs in, do it with your Model class -- e.g. call userModel.login(user, pass). If it succeeds, update the data in the model and navigate to the home screen (or any screen) and fetch the data from the Model with a ScopedModelDescendant.

from scoped_model.

You can close, it worked great! :D

from scoped_model.

Heya @RobertBrunhage -- did this help out? If so, I can go ahead and close it out. If not, please feel free to write back!

from scoped_model.