Fix data loss in connection with geo: intents. #21
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When geo: intents are handled by activities created in a different task, that can lead to the same map being opened multiple times (once in each task). The way the maps are implemented, this means that the last to call onPause/onDestroy will "win" its reference points will end up on disk. This is particularly annoying if that one is the one that has no reference points and you lost all that you added... Solve it via a horrible hack that always uses a new, clean task (of which there should be only one). Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When geo: intents are handled by activities created
in a different task, that can lead to the same map
being opened multiple times (once in each task).
The way the maps are implemented, this means that the
last to call onPause/onDestroy will "win" its reference
points will end up on disk.
This is particularly annoying if that one is the one
that has no reference points and you lost all
that you added...
Solve it via a horrible hack that always uses a new, clean
task (of which there should be only one).
Signed-off-by: Reimar Döffinger Reimar.Doeffinger@gmx.de