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
UI signals vs then #2671
Comments
From the docs for
Is it correct that you want to set the text of I'm not really an expert, but I would try to use
|
Thanks! That clears up the matter. Looks like I still do not entirely get how the Signals work :) As for "Is it correct that you want to set the text of self.label to the value of self.textField on each button tap?" - no, I wanted to change label text to text in text field in real time only after button was tapped before. Do you know of any RCA setup that specifies that? |
Ah ok, and once the button you want to keep updating the text label indefinitely, even if the button is tapped again? My first idea was to use I would try to use those, but you'll need to implement the predicate block yourself instead of just doing Maybe theres a better way that I don't know of though. |
Oh, seems like I was wrong (I was looking at my outdated local repo instead of the current one). Turns out, there is public func skipUntil(trigger: Signal<(), NoError>) -> Signal<Value, Error> implemented in However, it seems like you are currently using You could also take a look at Rex for UIKit Bindings for the Swift API |
Thanks again. I'll look into it. |
Why does below then construct work with custom signals but does not with UI signals (then closure is not even called there)? My goal is to wait for button tap before processing text from a text field.
The text was updated successfully, but these errors were encountered: