waittimer

DataSource is a class, not an object, so you must instantiate it before you can use it. The fact that it has a companion object is irrelevant to you, because the companion object doesn't have any public properties or functions.

FetchCompletionHandler is a callback function. The typealias just makes it easier to describe in code without having to write (FetchResponse?, FetchError?) -> Unit every time you need to mention the type.

Since the callback is the last parameter of the fetch function, you can call it using trailing lambda syntax. In this case, the lambda is your FetchCompletionHandler. The two parameters of the lambda are FetchResponse? and FetchError?, as defined in the typealias.

So, you'd use it like this:

You may declare the wait timer and its channel outside the if statement, and only initialize them if wait timer is needed. If not, the channel may remain its zero value–which is nil–because receiving from a nil channel blocks forever, so this case will never be ready (for details, see How does a non initialized channel behave?).

Okay, so I managed to find the solution to this one. The issue was that what I was returning was a Future. Even though it was a Future, and I was awaiting the response, the response was still in the future format.

So the resolution was as follows.

1) Create a new global variable of List that is set to the server-response.

Your stateModify function is not a method of _MyHomePageState. Also when you are accessing the _MyHomePageState().textChanger() in stateModify you are eventually creating a new object of _MyHomePageState() but not inserting in render tree.

You should use Timer instead of Timer.periodic. The Timer.periodic will repeat the task until the Timer.cancel is called. Timer will do a callback after the given time period which you require.

Pass the function textChanger when you are calling stateModify that way you will be able to call the function of _MyHomePageState without creating a new object.

Do the following changes.