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 point (node) drawing mode, when hovering over the halo of an area feature, the UI suggests that a point drawn at that moment will snap to the area outline, however, the point appears in the interior, no snapping occurs.
ssss.mov
Version
2.00-alpha3
What browser are you seeing the problem on? What version are you running?
Firefox 107 Mac
Steps to reproduce
Enter point drawing mode
Hover over the halo of an area feature
Click to draw the point
The browser URL at the time you encountered the bug
First, I have just cleaned up the snapping as best as I can for the mapathon this friday (whoo). The renderer will no longer get confused about whether it is targeting a parent way or area during a node dragging operation.
Note: Node snapping works a little funkily at the moment. I have filed #719 to track this. Basically, we need to rethink how we do our polygon rendering and targeting. There's more information there.
For now, you should be able to snap nodes to ways as normal, and areas will only 'snap' once you hover over the area fill. Like so:
node_dropping_onto_fill.mov
Downside- in wireframe mode, this means nothing is targetable! But that will get fixed in #719 as well.
Fixed in d72e896fb9289e6695eec6f38d2a169f8c9d8ca1. Incidentally this made the behavior of the fix for #702 even better- the way/area you're modifying will no longer 'flicker' as you drag the node around.
Description
In point (node) drawing mode, when hovering over the halo of an area feature, the UI suggests that a point drawn at that moment will snap to the area outline, however, the point appears in the interior, no snapping occurs.
ssss.mov
Version
2.00-alpha3
What browser are you seeing the problem on? What version are you running?
Firefox 107 Mac
Steps to reproduce
The browser URL at the time you encountered the bug
https://mapwith.ai/rapid-v2-alpha3#background=EsriWorldImagery&datasets=fbRoads,msBuildings&disable_features=boundaries&map=21.50/40.74004/-111.86053
The text was updated successfully, but these errors were encountered: