Calling controllers about mithril-hx HOT 5 CLOSED

I think it's the expected behavior, since you're bypassing Mithril's controller handling when creating the Test objects yourself and assigning them in a normal Haxe class. If you use routes, you may get a different result since all controllers are called again when the route changes.

The more I use mithril-hx, the less I'm relying on the controller method, since it works as a constructor in Mithril, which we already have with Haxe's classes.

from mithril-hx.

Using the router works as expected, but in this case it's not a good fit. I'm using it for developing a cordova app, where I have no use for routing really. I mainly use the controller method in cases where I need some stuff done when the components mounts/unmounts (for example adding/removing an event listener to the window object). The combination of controller/unonload is really useful for that. I could replace it by using config on the root element of the view (with ctx.onunload), but that means I'm relying on the component to be rendered first. So I'm unsure what the right way to do this would be.

from mithril-hx.

Ok, I see! Looking at https://lhorie.github.io/mithril/mithril.component.html#unloading-components it seems that you have to call mount again to make your case work, instead of using redraw (which is only view-related). Does it work to replace the M.redraw calls in your example with the same M.mount call?

from mithril-hx.

Thanks, I see. I've misinterpreted the use of the controller method. I've solved this for my case by calling a mount/unmount method on the components since they all pass through the same method. Something like this:

public function setView(view) {
  if (component != null) component.unmount();
  component = view;
  component.mount();
}

Thanks for the help and your work on the externs!

from mithril-hx.

Glad to help. :)

from mithril-hx.