docs: record the crosswalk inset dead zone
Sweeping the declared [0, 8] range and measuring where the group actually lands: 0 to 3.2 tracks one-to-one, and 3.2 to 8 does not move at all. No diagnostic, no feedback — roughly 60% of the advertised range is inert. crossingJunctionInset() drives it. targetDistance bottoms out once inset reaches the approach's cutback, and a 4m cap sits above that, so the real ceiling varies per approach while the manifest publishes a flat 8 for all of them. This is worse than the edge-offset case already on file. That one refuses and says so; this one silently does nothing, which is indistinguishable from a broken control — the exact failure the interval flag exists to prevent, occurring in the upper half of a range rather than across a whole handle. A user whose first drag lands in the dead zone concludes direct editing does not work. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
7b5bb753a7
commit
4b70b0221d
2 files changed
+57
-4
No files matched your search
@@ -56,3 +56,53 @@
|
||||
不是静默破坏。
|
||||
|
||||
已并入 `08-31-constraint-range-validation` 的需求。
|
||||
|
||||
---
|
||||
|
||||
# 追加:`junction-crosswalk-inset` 的静默死区
|
||||
|
||||
日期:2026-08-31,区域 `nantaizihu-9PTsZg`。
|
||||
|
||||
手柄 `handle:junction-crosswalk-inset:node/1140799725:segment:way/-3246/0`
|
||||
声明 `value.min = 0`、`value.max = 8`。逐值提交预览并测量该组 6 条斑马线的中心位移:
|
||||
|
||||
| inset | 相对 inset=0 的位移 | 增量 |
|
||||
| --- | --- | --- |
|
||||
| 0 | 0.00 | — |
|
||||
| 0.5 | 0.50 | +0.50 |
|
||||
| 1.0 | 1.00 | +0.50 |
|
||||
| 2.0 | 2.00 | +0.50 |
|
||||
| 3.0 | 3.00 | +0.50 |
|
||||
| 4.0 | 3.20 | +0.20 |
|
||||
| 5.0 | 3.20 | **+0.00** |
|
||||
| 6.0 | 3.20 | **+0.00** |
|
||||
| 8.0 | 3.20 | **+0.00** |
|
||||
|
||||
`0 → 3.2` 是干净的 1:1 线性响应;`3.2 → 8` **完全无响应,且无任何诊断**。
|
||||
|
||||
## 成因
|
||||
|
||||
`crossingJunctionInset()`(`native-road.js:1325`):
|
||||
|
||||
```js
|
||||
const targetDistance = Math.max(0, plan.cutbackMeters - inset);
|
||||
return Math.min(CROSSWALK_MAX_JUNCTION_INSET_METERS,
|
||||
Math.max(0, candidate.junctionDistanceMeters - targetDistance));
|
||||
```
|
||||
|
||||
inset 增至 `plan.cutbackMeters` 后 `targetDistance` 触底为 0,再增无效;
|
||||
外层 `CROSSWALK_MAX_JUNCTION_INSET_METERS = 4` 另有封顶。
|
||||
因此有效上界是 `min(cutbackMeters, …)` 的某个函数,**逐进口不同**,
|
||||
而 manifest 对所有进口一律发布固定的 `max: 8`。
|
||||
|
||||
## 为何比外缘偏移那例更严重
|
||||
|
||||
外缘偏移越界会返回阻塞诊断——用户看得到"不行"。
|
||||
本例越界**什么都不发生**:拖动手柄,几何纹丝不动,没有诊断、没有提示。
|
||||
与「控件坏了」无法区分。
|
||||
|
||||
这正是 `flag.ts` 为 `profile.interval` 立下的规矩所要避免的
|
||||
(「一个拖了没效果的控件比没有控件更糟」),区别只在于它发生在量程的上半段,
|
||||
而不是整个控件。
|
||||
|
||||
若用户在已处于死区的进口上首次尝试拖拽,得到的印象就是"直接编辑不工作"。
|
||||
Reference in new issue
Block a user