Currently, while the pause is very brief, there is a pause as the internal copy of the raindrop data is serialised to storage. This comes about because I'm doing the save in the add/edit/delete methods and doing it in an order that makes sense (so any issues will bubble before I report that the save was done).
Consider moving this operation into a thread.
Currently, while the pause is very brief, there is a pause as the internal copy of the raindrop data is serialised to storage. This comes about because I'm doing the save in the add/edit/delete methods and doing it in an order that makes sense (so any issues will bubble before I report that the save was done).
Consider moving this operation into a thread.