-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reactive_touch_spin doesn't display programmatic value updates #37
Comments
To recreate - edit the example app - example/lib/main.dart and make the sign up button update the value:
|
I don't think you'll be able to use flutter_touch_spin due to this issue. It kind of makes the widget, not a reactive_forms widget as it is unresponsive to reactive_forms. |
Hi @BenjaminFarquhar It seems that I will need to make PR one more time and release a temp substitution for the control) |
@vasilich6107 You're welcome! Sounds good! Sure, will do. |
@BenjaminFarquhar done |
@BenjaminFarquhar check latest version |
@vasilich6107 I will do thank you. I have confirmed it is working. Thanks for the quick fix. |
@vasilich6107 in version 0.4.0 I get the error: setState() or markNeedsBuild() called during build. When I go back to ^0.3.0-nullsafety.2 I don't get the error. I don't have time right now to investigate so I'm staying on ^0.3.0-nullsafety.2 as everything is working fine for me on that - changing the value from the outside is also working in that version. |
Could you provide reproduction code? |
@vasilich6107 The bug occurs when you run the example project and click on the + or - in the widget with the mouse |
@BenjaminFarquhar |
I do not know why author added setState call |
From flutter docs
|
@BenjaminFarquhar check latest version |
Cool, thanks @vasilich6107 |
reactive_touch_spin only displays updated values from clicking the up and down arrows to change the number, not from resetting the form values or calling updateValue() or any of the other numerous ways of changing the value programmatically using reactive_forms.
The text was updated successfully, but these errors were encountered: