deliverLatestCacheToView delivers all previously emitted items about thirtyinch HOT 4 OPEN

If the cache behaviour is intentional, then I think it doesn't match the documentation:

If the transformer receives a next value while the previous value has not been delivered, the previous value will be dropped.

You are right about the deliverLatestToView variant. There were multiple Observables involved - sorry for the noise. :)

from thirtyinch.

There is similar strange behaviour with deliverLatestToView (the variant without the caching).

Again, this delivers all of the items which should have been dropped while the view was detached, but it delivers them in a different order. Is this a threading bug?

11-02 13:53:57.080 D: Emitting 21ea0e8
11-02 13:53:57.086 D: Emitting 207a5a6
11-02 13:53:57.956 D: Emitting 1b0e394
11-02 13:53:57.973 D: Emitting 9f87632
11-02 13:53:58.746 D: Emitting 182a500
11-02 13:53:58.759 D: Emitting 3b3c37e
11-02 13:54:06.459 I: Delivering 21ea0e8
11-02 13:54:06.460 I: Delivering 1b0e394
11-02 13:54:06.461 I: Delivering 182a500
11-02 13:54:06.462 I: Delivering 207a5a6
11-02 13:54:06.463 I: Delivering 3b3c37e

from thirtyinch.

The deliverLatestCacheToView behavior is correct. All items, including the already delivered ones will be emitted again. Sending all items since the view was detached could be another operator. I'm waiting for a PR from you 😉

Can you post the code for your deliverLatestToView example? These must be multiple Observables because deliverLatestToView emits only the latest item. Neither the Observables nor the operators know each other. The order between emissions of different Observables cannot be guaranteed.

from thirtyinch.

• update documentation

from thirtyinch.