This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-07
Channels
- # aleph (15)
- # beginners (18)
- # boot (18)
- # business (1)
- # cider (11)
- # cljs-dev (13)
- # cljsrn (19)
- # clojure (14)
- # clojure-austin (8)
- # clojure-dusseldorf (1)
- # clojure-finland (1)
- # clojure-greece (118)
- # clojure-poland (3)
- # clojure-russia (46)
- # clojure-spec (65)
- # clojure-uk (18)
- # clojurebridge (3)
- # clojurescript (16)
- # cloverage (7)
- # core-async (8)
- # cursive (74)
- # datomic (28)
- # editors (3)
- # emacs (3)
- # ethereum (5)
- # hoplon (19)
- # jobs-rus (18)
- # lein-figwheel (1)
- # off-topic (2)
- # om (107)
- # om-next (4)
- # onyx (23)
- # pedestal (23)
- # proton (3)
- # protorepl (1)
- # re-frame (108)
- # reagent (10)
- # ring-swagger (15)
- # spacemacs (2)
- # specter (11)
- # testing (7)
- # untangled (79)
- # vim (4)
- # yada (53)
does anyone else have problems with TextInput
and reagent?
when I use {:value @my-atom :on-change-text #(reset my-atom %)}
I see that the input fields "can't keep up" with my keypresses
i.e. when you type quickly, the field skips over chars
my hypothesis is that this is due to reagent's ratom-based update mechanism
whereas I think if you use react component state as in http://stackoverflow.com/a/35713280/239678, the mechanism works
did you run into this issue @knotschi ?
@pesterhazy maybe animated value can help with it?
I'm bot sure that this is will work, but you can try. In theory if you use animated value, then they not rerender all, thay just set value over bridge. Wait a minute for snippet
But anyway I'm not sure that you can use animated value for textfield value)
What I know for sure, that recently I create custom views for ios and android, and used animated api to change value over bridge, instead full render
I'll check it out
Just tried using reagent.core/flush
after swapping in the global state values
that seems to mitigate the problem somewhat
hang on
it actually works
you need to make sure though to set the value to ""
instead of nil
when resetting the field
flush
seems to fix the issue