@gadfly361 thanks for your help. I fixed the issue: for the select element, I used on-click event, after read the react doc, I changed it to use on-change event. then it works on both PC and mobile. I am using a physical phone & physical tablet. Just wondering why on-click works on PC but not on mobile.

I,m having issue with what reframe call a form 2 component

I want to call functions when the internal state has precise value

I'm using a cond

the :else expression is called

the internal state is update

but the component isn't re-rendered

what i'm doing wrong

We'll probably need to see a minimal example of code

version 0.5.1.rc2 about to be released. Please test it on your apps.

<!channel>: ^^^^

Okay 😄

please don't use at-channel, it notifies almost 200 people

@mikethompson: just curious, got a changelog for 1.5.1? Didn’t see it on github

Oh, sorry, here it is: https://github.com/reagent-project/reagent/blob/master/CHANGELOG.md.

I’m excited about the [:input] cursor stuff, have been shamelessly aping the implementation inside re-com without really understanding it 😐

@voidlily: this is the reagent channel

I actually did want to notify 200 people about the need to test 0.5.1.rc2

@timgilbert: that's good that you've been testing it. I came up with the solution, but it actually isn't something we use very much. So your further testing is good.

@timgilbert: Personally, I'm most excitted about the better error reporting (the "path" to the component will now be given when an error occurs in rendering)

We'll fold that change into re-com at the very first oportunity

@wqhhust awesome! Glad you found a working solution

@mikethompson: I finally find what happend. The issue was that i was updating the local state, then on the following render i was taking it into account

I'll make a gist to make it more clear

https://gist.github.com/benzen/dac5018371fd124fa3c7

@mikethompson: maybe it's a kind of error that we could add the rookies mistake section of the wiki of reframe

if so, tell me and I'll be happy to trim my example to make it more easy to grasp

There's a fair bit of code in that Gist. I'm not clear on the problem.

Ok, so I'll trim it later today and post a new version

in reagent-forms, can I set a field attribute (e.g., rows for a textarea) based on a key in the ratom?

more generally, I suppose the question is: as I understand it, bind-fields uses the field :id value to pick out a key from the ratom... is there a way to do that more generally for attributes

my events-fn passed to bind-fields is catching the events and updating the state correctly, I'm just not successfully using that value.

@mikethompson: I've updated the not-example part https://gist.github.com/benzen/dac5018371fd124fa3c7, do you think it's enought ?

You say "this won't work" but I don't know what problem I'm looking at

I guess I could puzzle over this for 10 mins and figure out what the intent is, and then what the problem might be. But most readers won;t have the time -- you really have to spoon feed people (like me ... I'm lazy)

I agree

@mikethompson: https://gist.github.com/benzen/dac5018371fd124fa3c7 is it better ?

@benzen: To be an example of a rookie mistake, it has to be so simple that a rookie can understand it. That means it has to be about 5 lines code long and hit you between the eyes. I can see various puzzling things in that code, but it is all waaay too much, and to be honest I'm still not exactly sure of the specific point you are trying to highlight. If I don't immediately get it, a rookie won't.

@benzen what are (on-right) (on-left) calls trying to achieve in the first example? don’t they cause re-rendeing? also swap on L29 looks suspicious. Component should not change its state during render call. It can do that in response to events, but should not do it during rendering itself.