You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #8594 we discovered that there doesn't seem to be any mechanism for signals to be reconnected when a model is replaced on another model. For example when replacing the glyph on a GlyphRenderer or the tile_source on a TileRenderer, the renderer should unsubscribe to events on the old model and re-subscribe to any change events on the model but there doesn't seem to be such a mechanism at the moment (unless @bryevdv and I missed something).
It would be nice if a property could handle this automatically by discovering the signals connected to the old model and then setting up those same signals for the model its being replaced with but I know nothing about the feasibility of such a mechanism.
The text was updated successfully, but these errors were encountered:
In #8594 we discovered that there doesn't seem to be any mechanism for signals to be reconnected when a model is replaced on another model. For example when replacing the
glyph
on aGlyphRenderer
or thetile_source
on aTileRenderer
, the renderer should unsubscribe to events on the old model and re-subscribe to any change events on the model but there doesn't seem to be such a mechanism at the moment (unless @bryevdv and I missed something).It would be nice if a property could handle this automatically by discovering the signals connected to the old model and then setting up those same signals for the model its being replaced with but I know nothing about the feasibility of such a mechanism.
The text was updated successfully, but these errors were encountered: