Event conflation

[genaku]

Event conflation

[elizarov]

I don't think that you need an actor to keep track of a synchronous updates that should happen in your application. Actors are designed to help you manage your asynchronous jobs. If you have a switching button with 3 states then you should directly change its state on every click without adding a layer of indirection via actor. You should use an actor to launch whatever asynchronous job you need to be tied to those synchronous changes in state.

[genaku]

Thank you for answer. I used button to check technology. Actual use is RecyclerView filled by query from database. Tap on item of RecyclerView update field of record in database (UI state) forcing to refresh RecyclerView item state. At the same time this tap on RecyclerView item should try to change long time task.