-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
And undocumented causality loop in layout computation #83
Comments
As a general rule, one should usually avoid It's kind of an accident of the way they get constructed that the widget monads have MonadSample instances, and it's possible we ought to find a way to simply disable those in ordinary widget code. (The correct and safe place to use sample is typically inside the corresponding push/pull monads.) |
That is exactly my experience -- thank you for the relief of not being alone in the suffering! : -) |
If you have a Dynamic and want to use its value from the widget code, usually you want to first make sure that the Dynamic is passed down as far as reasonable to the widget that it ought to have an impact on, and then possibly use |
@cgibbard, by the way, I have hoogled for
|
Apologies, I was thinking of https://hackage.haskell.org/package/reflex-dom-core-0.8.1.0/docs/Reflex-Dom-Widget-Basic.html#v:dyn which for some reason is exposed in Reflex as |
The following is not a causality loop:
..but this one is:
I guess this can be somewhat surprising to the user, since the semantics are not exactly explained in the documentation.
The text was updated successfully, but these errors were encountered: