`ViewObservable.text()` does not work with `Observable.delay()` about rxandroid HOT 3 CLOSED

delay(delay, unit, AndroidSchedulers.mainThread()) can solve your problem. It will run the work in the UI thread.

from rxandroid.

It was my mistake to make ViewObservable.input to return Observable<String> instead of Observable<CharSequence> and I agree that it should Observable<CharSequence>. But I don't like the idea that a TextView itself should be emitted. Then reason I made ViewObservable.clicks to return Observable<View> is that there is no any another value to emit when the View is clicked. Of course, it could be Observable<Void> but it seems a bit weird for me.

I think we should change the return type of ViewObservable.input to Observable<CharSequence> (and probably rename to ViewObservable.text) and remove the existing ViewObservable.text method. I know that it's a breaking change, but it shouldn't be difficult to migrate.

from rxandroid.

I did a little bit more investigation into this and delay(delay, unit, AndroidSchedulers.mainThread()) did not work either. The Scheduler parameter only schedules the delaying, but the issue is the mutable value being emitted since .getText() can return an Editable.

If you include an extra map to .map(CharSequence::toString() or .map(SpannableString::new) before the .delay(), everything works as intended. I think the best solution is to return a cloned CharSequence via new SpannableString(CharSequence), or to return the instance directly and include a disclaimer that it may be mutable.

from rxandroid.