mapbox / mapbox/mapbox-plugins-android
Changing to 10000 symbols after zooming in BulkSymbolActivity.java exits activity
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 242
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Background
The BulkSymbolActivity.java is quite performant on all zoom levels for the 10, 100, 500, and 1000 symbol quantity options provided in the dropdown. The 10000 option also works performantly in some cases, but causes the activity to exit after certain zoom interactions. A couple of different scenarios to reproduce the problematic behavior are presented below.
Steps to reproduce
Switching to 10000 symbols when zoomed in
Select any symbol quantity other than 10000, and then zoom into the map. Then, select 10000 from the dropdown, and the activity will exit back to the Annotation plugin list view screen.
Zooming out when using 10000 symbols
If the 10000 option is selected from the dropdown before zooming in, the symbols render after a few seconds. The map can then be zoomed in successfully with only a small amount of lag. However, attempting to zoom back out causes the activity to exit back to the Annotation plugin list view screen.
Although 10000 symbols in a geographic area as condensed as Washington DC is likely not a very common use case, the issue is worth addressing given that the behavior is not currently well-documented or explained. I could not find any log messages that explained the behavior, so even being able to better understand the exiting behavior would be a step in the right direction.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with BulkSymbolActivity.java and reproduce both reported scenarios: switching to 10000 symbols while zoomed in, and zooming out with 10000 selected. Trace why the activity exits and identify any available diagnostics; done means the problematic interactions no longer unexpectedly return to the Annotation plugin list, or the behavior is clearly documented if it cannot be prevented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100