This repository has been archived by the owner on May 4, 2022. It is now read-only.
@PutModel and @GetModel returning to Main Thread #54
Assignees
Labels
Comments
smaugho
added a commit
that referenced
this issue
Mar 7, 2017
…notation, Close #79 Change Action $GetModel to $LoadModel, Close #77 Change @Populator to @populate and @recollector to @recollect, Close #76 Change the name of @JsonSerializedModel to @jsonmodel, Close #68 Method Get with Fields should put the passed fields as an from URL encoded, Close #66 Add Failed Action Selector for Events, Close #64 Add the Event fields to the Action Selector for easy access, Close #63 Pass the created event as parameter to the Finished Action Selector, Close #62 Array declarations not working in Actions, Close #61 $GetModel and $PutModel always populate and recollect, Close #59 Crash calling fragment in Actions, Close #58 In the adapters (for AdapterViews and RecyclerView) it is important to check if the position is valid, Close #57 $Notification action doesn't have setStyle method, Close #56 @PutModel and @GetModel returning to Main Thread, Close #54 @JsonSerializedModel improvements, Close #53 @OverrideAction to directly override methods, Close #39 "withResult" for Activity Actions, Close #36 NavigationDrawer Error for latest support libraries, Close #1
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
By default @PutModel and @GetModel returns to the Main Thread. This is a very useful feature when the current view it is a Fragment or Activity, but it is not useful inside Beans or other Enhanced Components is not useful and can degrade the responsiveness of the app.
The text was updated successfully, but these errors were encountered: