Docs: add walk-through examples on Canvas redraws #75
Conversation
| You can cause these updates to be processed at regular intervals---if | ||
| julia isn't busy doing something else---as follows: | ||
| ```jl | ||
| eventloop = Timer(_->Reactive.run_till_now(), 0.001, 0.001) |
There was a problem hiding this comment.
In the latest commits, I put this in Reactive.init.
The reason is, if one is using multiple packages that run Reactive.run, then they might end up stepping on each other's run calls. I also made it so that push!(...) takes an optional third argument which is a callback that will be called in case of an error... By default this callback prints the error to STDERR.
I was thinking the reason for exposing Reactive.run is to allow packages to watch for crashes, but this seems like a worse idea than having the onerror callback.
There was a problem hiding this comment.
In the latest commits, I put this in Reactive.init.
I was going to suggest that (for the reason you cite), glad you've already thought of it.
There was a problem hiding this comment.
Oh, and if you think this has any tutorial value at all, I can make changes as you change the API. (I won't bother if you think it won't be useful, though.)
There was a problem hiding this comment.
We should definitely update this for the new changes and merge this. This will be very useful for library writers using Reactive.
|
Reactive is meant to be orthogonal to other packages. But when you are making a GUI-like package such as ImageView, you will need to think about precisely these things. It will be nice to have this documentation. |
|
Glad it seems useful. I will definitely revise this and resubmit. |
| c = new(io, n1, n2) | ||
| combined = merge(n1, n2) | ||
| throttled = throttle(1/60, combined) | ||
| Reactive.preserve(map(x->println(c.io, "state1: $(value(c.state1)); state2: $(value(c.state2))"), throttled)) |
There was a problem hiding this comment.
I find the use of the value slightly awkward.... But it's really OK. Here's an alternative
show_canvas(c) = map(render, sampleon(throttle(1/60, merge(c.state1, state2)), Node(c)))
(I find it better to take out the rendering from the type definition as a personal preference)
There was a problem hiding this comment.
Oh wait, you'd still need value inside render. Never mind me.
timholy
force-pushed
the
teh/imageview_warmups
branch
from
67e6cc0 to
6241b42
Compare
|
Indeed it's much simpler now. |
|
bump |
Note: this PR is against the "next" branch.
FRP is new to me, so as I struggle to wrap my head around it I thought I'd create a "diary." If that diary is useful to others, great; otherwise, feel free to close this.