well I ended up just making a component that derefs an r/atom that contains a buffer of all the transactions and then immediately runs the transact! fn on the buffer and then clears it. then you just have to make sure to add the [transactions] component to the main app state.

i mostly just want them to all happen at the same time so that none of the reactions to the tx report queue get skipped

in this om next is clearer

ops sorry thinking out loud 😄

actually maybe I'll just use js/setinterval

@mpdairy: > does anyone know how I could make a non-component function run after every react update With reagent, the components update in response to the state updates. So wouldn't you simply listen to changes in the state? Seems off to me that you would be listening for components running ... when they are simply a symptom of something else occuring.

Having said that .... with release 0.6.0 of reagent (currently in SNAPSHOT), you can provide a function to be run AFTER the next annimation frame (components get updated). Would that do?

https://github.com/reagent-project/reagent/blob/master/src/reagent/core.cljs#L320-L325

Oh, yes, thanks @mikethompson that's just what I was looking for!

though I guess I'll have to wait for it to get out of snapshot

If you want to use it now: - clone the reagent repo to your machine - do a lein install on your machine (which will put it into your local Maven repo) - change the deps in your project's project.clj to be for the 0.6.0-SNAPSHOT

Having said that I can't vouch for its stability. I haven't tried it.

right, well I'd want to include it in my "posh" library so I'd better just stick with the js set interval for now and then hook into that function later. it is exactly what I was looking for

@mpdairy: I can't vouch for it but ... reagent.impl.batching/do-after-flush might well give you the same functionality in v0.5.1

https://github.com/reagent-project/reagent/blob/v0.5.1/src/reagent/impl/batching.cljs#L78-L79

Oh, sweet, that does look promising

Correction: looks like you should use: do-later

Hmm. Actually, I can see pros and cons to the two functions, depending on your needs

so, i was wondering, if you have a reaction and something updates it several times between render frames, would it only end up reacting to the last value that the reaction ended up with?

Yes

ok good, I think that was my problem then

what's the difference between do-later and do-after-flush?

Oh, happy thanksgiving

Not in this part of the world

do-later will schedule an annimationFrame

do-after-flush won't

Ooh I worked remotely for a foreign company last year and it was always a shock when they weren't celebrating our holidays.

So do-later will run fwithin 16ms Whereas do-after-flush just puts f onto the end of the animationFrame whenever that might be ... but something else will have to trigger that annimationFrame.

So, the right one depends on your requirements

will do-later keep calling f after every frame?

or maybe I could have f call do-later

do-later is a one off

So your f would have to reschedule itself, via another call to do-later

Anybody used (react-)quill with reagent?