[Store] Use MainActomaton
#65
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Successor of:
MainActomaton
#64Overview
This PR replaces
Store
's usage ofactor Actomaton
with@MainActor class MainActomaton
which is introduced in #64 for:StoreConfiguration
#40StoreConfiguration
actor Actomaton
may sometimes cause old state updates when:StoreConfiguration.updatesStateImmediately = true
andIssue 2b. has been observed when performing Actomaton-Gallery's LineCollisionExample which runs in 60 frames per seconds (by timer) + additional user-object-dragging, that led to too high update frequency.
While
Store
could update states on main-thread immediately byupdatesStateImmediately = true
, non-main-threadActomaton
may send older state back toStore
due to slow operation, so this caused the malformed state update onto UI.