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
Sometimes we may want to have a gesture interact in a unique way with a layer or plugin. I guess think things like onTap, onLongPress and a circle layer, or polygon layer, or custom plugin/widget layer.
Flutter_map has its own gesture code, and it would feel clunky to recreate gesture code within each layer/plugin (i.e every plugin/layer to have it's own onTap,onDoubleTap,onLongPress etc). Lots of duplicated options, maybe lots of duplicated code (although some could be in a separate referenced func somewhere).
Each plugin may have a separate set of objects to handle. For example again, lets suppose we want to add an onTap to a polygon layer, it would make sense to only process polys that haven't been culled, which is an internal private object (may we could expose some internal variables via getters though...). If it's a circle layer, we will be looking at a different set of objects.
Does anyone have any interesting thoughts around this, how there can be an elegant solution to interfacing gestures with layers and plugins ? Or is it something flutter_map shouldn't get too deeply involved with (as it will just become a big mess :D) ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Sometimes we may want to have a gesture interact in a unique way with a layer or plugin. I guess think things like onTap, onLongPress and a circle layer, or polygon layer, or custom plugin/widget layer.
Flutter_map has its own gesture code, and it would feel clunky to recreate gesture code within each layer/plugin (i.e every plugin/layer to have it's own onTap,onDoubleTap,onLongPress etc). Lots of duplicated options, maybe lots of duplicated code (although some could be in a separate referenced func somewhere).
Each plugin may have a separate set of objects to handle. For example again, lets suppose we want to add an onTap to a polygon layer, it would make sense to only process polys that haven't been culled, which is an internal private object (may we could expose some internal variables via getters though...). If it's a circle layer, we will be looking at a different set of objects.
Does anyone have any interesting thoughts around this, how there can be an elegant solution to interfacing gestures with layers and plugins ? Or is it something flutter_map shouldn't get too deeply involved with (as it will just become a big mess :D) ?
Beta Was this translation helpful? Give feedback.
All reactions