Hello, I am working on Om application that uses react-motion to animate a component transitions. The problem is that nested/children components that are inside animated component are not re-rendered when their local state changes e.g. with "om/set-state!". Application state is stored in single tree. When application state is altered via cursors then re-rendering is performed.
I suspect that problem could be that react-motion does something strange that breaks React or it is a problem with interaction of react-motion with Om components. So the question is, how handling of local state is different in Om components vs. plain react components? How can I diagnose this problem? I use Om 0.9.0 (with React 0.13.3, and react-motion 0.3.0), on page load React issues warnings that likely caused by react-motion: > Warning: Don't set .props.children of the React component. Instead, specify > the correct value when initially creating the element or use > React.cloneElement to make a new element with updated props. > Warning: Don't set .props.__om_init_state of the React component. Instead, > specify the correct value when initially creating the element or use > React.cloneElement to make a new element with updated props. -- 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.
