@darwin thanks!

@sooheon: I guess what you could do is in the on-change dispatch to do nothing unless all characters are complete characters. Or alternatively ignore all on-change and use only on-blur.

@sooheon: also, please let me know when you find a solution

@sooheon are you using :value or :default-value on the input? I guess :value could cause this behavior

@nberger: using :default-value how would you reset the input's value from the outside?

@mbertheau I guess you have to rely on something else. But in many cases you don't need to do that. In this particular case, is it needed to be able to reset the value from the outside, after the initial render of the component?

@nberger Yes. I guess I could trigger a re-mount with a different key.

Yep, that would be a way

if I change a value like that : (set! (.-value el) var)

is it possible to make it trigger the on-change event on el ?

the purpose of the event is to add the value of a clickable var into the currently focused input

I couldn't come up with a "re-frame way" of doing that

I hoped that the on-change event on the updated input field would trigger when the text changes but it doesn't

I don't like the approach but I'm not sure if there is a way to achieve this with handlers

@yenda Is that a paste function?

Yes kinda

It inserts the value you click on in the input field you are typing

But it doesn't trigger the on-change event on this field so it is not handled

Which is my problem

@mbertheau do you know of any example of similar paste function ?

@yenda: And you have two problems doing that the re-frame way - finding the right spot in app-db for activeElement and knowing the selection to insert in the right position, correct?

@yenda: maybe in the component you could add a callback to the DOM element that dispatches the on-change manually and call that in on-mouse-down.

@mbertheau: yes that is exactly my two problems

which are solved by that function but I find it really ugly

i have not used callbacks yet but I'll give it a try

I agree it's ugly

😄

@mbertheau: I'm resetting :default-value using the will-receive-props react element method

like this:

(let [state (reagent/atom {:value (or default-value "")})]

     (reagent/create-class
      {:component-will-receive-props
       (fn [_ [_ props]]
         (let [default-value (:default-value props)
               state-value   (:value @state)]
           (when (not= default-value state-value)
             (swap! state assoc :value default-value))))

This changes the value from my component state when the wrapper component changes the default-value it is passing to it

My use case is that I have a generic input with state

And want to control it's value sometimes (e.g. search query string changes)