Allow updating inividual marker's position (like widget re-build)

[atototenten]

What do you want implemented?

Allow updating the individual "Marker"s' "position" .

What other alternatives are available?

Re-build the whole map ,through "Listenable.merge" ,tracking all the markers' position-listenable .

Thanks

[JaffaKetchup]

Hey @atototenten, it should be possible to wrap the MarkerLayer in whatever widget you need. Is this what you're looking for?

[atototenten]

Hey @atototenten, it should be possible to wrap the MarkerLayer in whatever widget you need. Is this what you're looking for?

This is what im currently doing ,re-building the whole marker-layer of the map ,through "Listenable.merge" ,tracking all the markers' position-listenable .

,but its still in-efficient compared to targeted updates right ?

[atototenten]

@JaffaKetchup any thing to say ?

i also find the explicit passing ,of marker size/alignment ,to be imperfect API .since its either static ,or difficult to calculate info. .

thanks

[JaffaKetchup]

This is not really possible without adding some way to keep track of the marker, as at the moment, the layer just puts the child at the location specified by the wrapping Marker. A significant rearchitecture would be required to enable something like this, such as adding a key then changing the way the layer works.

There's 2 open/draft PRs which make changes like this (one of which goes a step further), which you may be interested in.

Off the top of my head, without looking at the code, I couldn't tell you how inefficient changing a marker in a layer by wrapping the layer is.

Is there a performance problem you are actually having? If so, an MRE would be great.

[atototenten]

A significant rearchitecture would be required to enable something like this, such as adding a key then changing the way the layer works.

I understand .

this is not urgent .

should the issue be kept open ,or closed ?

thanks

[JaffaKetchup]

We'll keep it open for now, it's another target for a marker layer rewrite. I'll organise it when I get a moment.

Although I have just remembered Marker.key exists. Probably not massively useful given how I think (off the top of my head) we're doing things but...

[github-actions]

This issue requires additional information in order to be resolved. However, there hasn't been any response within the last 3 weeks.
If this issue still persists, please provide the requested information. This issue will be automatically closed in one week if there is no response.