Hans Raaf

Afaik, that is not possible right now. But I think you can easily make a fork and remove the [ServiceWorker part](https://github.com/maxence-charriere/go-app/blob/2c1f1d9faccea9f0f61441699839316577cb5047/pkg/app/gen/app.js#L13-L15) to give it a try. I think that could...

If you see `call to released function` in your console log, this means that an `app.FuncOf()` function was released and later called again. You should maybe add [dbg.log()](https://github.com/metatexx/go-app-pkgs/tree/master/dbg) where you...

A Func is release through calling Func.Release(): ``` go var f = app.FuncOf(func(app.Value, []app.Value) interface {} {return nil}) f.Release() ``` I wonder if you actually use `app.FuncOf()`. Your description sounds...

I have to confess that the code goes over my head. I was also warry about the nested async calls. I think I would try to figure out where in...

This is how I understand it: Exported field = Anything you set from outside (but don't change it inside, ever!) by setting a new component "over" the still mounted one....

I guess that is the same, many people stumble over. Make the `Select` lower case... and read: https://github.com/maxence-charriere/go-app/issues/672#issuecomment-1015483889

Well, I have such implementation for evaluation in my version and it works well. I was thinking about it being too cumbersome but having the render routine in one long...

I think that using something like this makes more sense than the `app.If()` construct and that `app.If()` should be deprecated and give such an example ;-) ```go func (c *thing)...

This would be up to 50 calls to Render (and possibly complex code) per second, not to waste. I have debugging code on the calls, and it does look awful...

I came up with some solution that seems to work. Maybe you can have a look at it or get inspired by it :)