feat(junction): edit complex crossing facilities
This commit is contained in:
1 parent
bb5dc01c07
commit
49a44fdf73
16 files changed
+307
-39
No files matched your search
@@ -285,10 +285,12 @@ requests so a cluster never falls back to the last selected road or node.
|
||||
|
||||
Complex JunctionTools consumes the same v2 `EditSession`, `PreviewRequester`,
|
||||
`ParameterPanel`, and map handle callbacks as ordinary junctions. Editable
|
||||
handles are `cluster-carriageway-width`, `cluster-carriageway-cutback`, and
|
||||
`cluster-corner-radius`. The first two use a `cluster-carriageway` anchor; a
|
||||
handles include `cluster-carriageway-width`, `cluster-carriageway-cutback`,
|
||||
`cluster-corner-radius`, `cluster-crossing-inset`, and
|
||||
`cluster-stop-line-offset`. The first two use a `cluster-carriageway` anchor; a
|
||||
corner anchor is resolved to its representative carriageway only to create the
|
||||
snapshot. Before edit mode, a selected cluster loads its scoped manifest so
|
||||
snapshot; crossing controls use `cluster-crossing` and its stable
|
||||
`crossingKey`. Before edit mode, a selected cluster loads its scoped manifest so
|
||||
`canEditJunction()` can use an editable server handle as the capability signal.
|
||||
Do not add a cluster-local draft, preview, undo, or save flow.
|
||||
|
||||
|
||||
Reference in new issue
Block a user