I suspect now what will happen is your app will not progress any farther once it starts up. It will constantly display the loading screen because, your code is returning 'null' in the init() function for one reason or another. That is what I suspect at this point in time.
Hi Greg, I have the same thought as well when I hit the error, which I have returning null from the init() function. However, I couldn't find it after I have checked the code many times. Really have no clue where the null coming from. Anyway, since this issue can be resolved easily so I would work with the solution, even it could be just a workaround.
Btw, I have another problem with hot reload.
I found that when hot reload the view is re-created as intended:
However, the initApp is not called after the recreation of view, since it is responsible in calling the AppController.init, failed to call it may give problem to the app, since most of the state value is reset after the recreation of view.
Do you see this a problem?
Sorry, I mean the AppView.Init is not called
This code in a controller object you wish to run with every hot reload. Possibly, you have it in the wrong controller? Without making such a change as you did above, simply place whatever code that seems to be necessary to run again with every 'reload' in the 'initState()' of the controller indicated in the screenshot.
You see, looking at your modifications, the code in the 'init()' is obviously not 'asynchronous operations'. Anything in the 'init()' should return a type of Future<bool>, and yet you've placed in the initState() of the AppView?? I'm sorry, but that doesn't make sense to me.
Above now is a sequence of screenshots conveying the 'path of execution' for a hot reload. I'm running 'an example app' called ContactsExampleApp. You can see its AppView's init() is being fired with every 'hot reload'. I don't understand the problem you're experiencing.
in _ContactListState:
Hope you are clear now. Thanks!
I've been attempting to run the app copy I received, but I'm receiving a git error I'm not familiar with, "git rev-list --max-count=1 version3" It doesn't know with the argument, 'version3', means: fatal: ambiguous argument 'version3': unknown revision or path not in the working tree.
Have you encountered this error before?
Hi Jason. I found the problem. It's apparent 'the solution' I had first given with version 2.0.0 ( State createState() => App.createVW(); ) was not efficient or effective enough! Admittedly, I didn't like it. I took the day to 'step back' and take the approach I originally intended. It involves only changing 'how' one would start an 'MVC' app:
Thus, in the main.dart, you'd see the difference:
I'll have a demo and the source code available shortly. For example, it's been tested successfully using your demo (debugString = "Value before init()")
mxc_application 3.0.0 is now available.
Hi Greg, I am trying to use your DBInterface for sqllite together with Bloc, and I am having a few issues I hoped you might be able to assist with. I have read from the comments on your Medium article that you don't advocate Bloc, but that it should work. My issue is that when the app starts it call the Open() function from DBInterface in the first screen to load and use DBInterface, and then I try to call the rawQuery from DBInterface using my Bloc class, and it tries to call Open() again, and it then proceed to try the query it itself, but return that the table I try to query does not exist. Any help you can give will be appreciated
@EsbenSoeltoft Hello, Esben. Would you have the source code on bitbucket or github? Nothing like 'walking through the code' to determine what's to be do. What are the 'errors' you're encountering? Opening the DBInterface again and again, for example, should not be an issue.
Hi all,
I'm learning life cycle in widgets.
I print the value of boolean property mounted in constructor method, initState() method, build() method, deactivate() method and dispose() method.
In dispose() method, it prints the value as true. how can it be? because, dispose()method suppose to remove the widget from the widget tree.
@override
void dispose() {
super.dispose();
print("dispose() secondPage mounted: "+ this.mounted.toString());
}this prints dispose() secondPage mounted: true
can anyone explain how this happens?
Yes, I don't readily know that answer, Kaweesh. I'm sure the much larger gitter community, Flutter, will have an immediate answer for you.