Support for tap regions
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 283
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
First we are using com.qozix.tileview.TileView, but want to move to a newer library to mitigate the risk of using an older library that is not supported.
Since we are using Compose heavily this library caught my eye.
My Question: do you think this library would be able to extended to support a tap listener when a tap occurs in a rectangle (and the rectangle may cross tiles)? In a map scenario, image that you have metadata about the map and that you want to display a bottomsheet that changes the info displayed as the user taps on areas of the image. For example they tap near a city name and info about the city is displayed.
The tap region would not be visible (no marker, callout, or path). It would virtual data associated with the image.
I guess I could implement MapUI.content. Yes?
Contributor guide
No contributing guide indexed for this repository
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 by reading the MapUI.content entry point mentioned in the issue and inspect the library's existing interaction support for markers, paths, or other map content. Determine whether invisible rectangular regions that cross tiles fit the current content model; done would require a defined API and behavior for receiving taps and identifying the associated region.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100