Pierre Laurence

I would only set the visibility of markers to GONE or VISIBLE because adding and removing the markers causes the parent layout to recalculate its size.

The library can be extended to support regions. Since regions are basically closed paths which may be filled or not, stroked or not, and for which tap evens are handled...

I'm curious to know about the use case. Is the map a complete world representation? This requires significant changes in how the library works internally. Also, in a flat space,...

Better late than never, I finally implemented infinite scroll. It required significant changes and was quite challenging. It will be available in v.`3.1.0`. A new "Infinite scroll" demo shows how...

Interestingly enough, I don't get the crash when I zoom-in manually. The crash only happens when I click on green clusters (at least for me). EDIT: I also get the...

It seems that we're hitting an internal limit due to how compose computes constraints. Width and height values need to hold on 32 bit at some point, which clearly cannot...

Coercing values would mean incorrect rendering by the layout. The Compose framework raises an exception, to notify that it no longer handles the input. I'm not comfortable having incorrect rendering.

As far as I can tell, the MapView cannot be reconfigured, so the message is missleading. After calling `destroy`, you have to create a new instance of MapView.

It looks like the route is made of a series of paths, because the route isn't continuous. Perhaps some `addPath` calls are missing. Can you reproduce the issue in a...

Oh you're using MapComposeMP. You posted the issue on the Android native version, which is probably not affected by this issue. Nevertheless I'll have a look.