Well that didn't work :D
I actually got that the wrong way around.
Looks like the best way to pass the correct value is to use destructuring to
get access to the value at the time the function is invoked and pass that value
along to any handlers, not the atom/cursor (or use something like (into {} ..
) to get a snapshot.
On Thursday, February 6, 2014 7:36:21 PM UTC-8, David Pidcock wrote:
> Yes, I am still getting my head around this -- that the rendering of the item
> can be out of sync with the atom it was handed is still a little wonky to me.
> :)
>
> I'm wondering if it isn't better to simply avoid the destructuring and pull
> out the data with (:key @atom) everywhere. I will experiment with that some
> to see if that makes it more accurately reflect actual state.
>
> On Thursday, February 6, 2014 5:23:38 PM UTC-8, David Nolen wrote:
> > Cases like this are to be expected and may need to be explicitly handled.
> > Dereferencing data will always give you something current which may not be
> > what the handler closure was given.
> >
> >
> > David
> >
> >
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/clojurescript.
