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
Clamp a repositioned event dropped before its predecessor's end
Aligns the drop gesture with the hard-constraint behavior of established
Gantt tools: a successor dropped in violation snaps forward to the first
valid position instead of keeping a violated arrow.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RDEgka4iDRFrenWeWFhunq
Copy file name to clipboardExpand all lines: docs/data/scheduler/experiments/experiments.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Finish-to-Start dependencies on the timeline. The dataset covers every route sha
22
22
23
23
## Timeline auto-scheduling (#22857, #22858)
24
24
25
-
The Finish-to-Start auto-scheduling engine. Moving or resizing an event pushes its violated successors forward on the drop, transitively, as one atomic change — and only when the relationship is actually broken: dragging `Plan` slightly to the right lands inside `Build`'s slack and moves nothing, dragging it past `Build`'s start pushes the whole chain. Moving a predecessor earlier never pulls its successors back. The `Design` diamond reconverges on `Integrate`, which settles once behind the later of its two branches. `Audit` is read-only: pushing `Setup` into it leaves it in place with the violated arrow visible, and nothing beyond it moves. The all-day pair shifts by whole days and stays all-day. Dragging a terminal to close a cycle (for example `Deploy` onto `Plan`) is rejected with a transient toast. The feature has no public API yet, so the demo feeds the internal store parameters.
25
+
The Finish-to-Start auto-scheduling engine. Moving or resizing an event pushes its violated successors forward on the drop, transitively, as one atomic change — and only when the relationship is actually broken: dragging `Plan` slightly to the right lands inside `Build`'s slack and moves nothing, dragging it past `Build`'s start pushes the whole chain. Moving a predecessor earlier never pulls its successors back. Dropping a successor onto or before its predecessor snaps it forward to the first valid position: the drop cannot create a violated arrow, while violations already present in the data are left as-is. The `Design` diamond reconverges on `Integrate`, which settles once behind the later of its two branches. `Audit` is read-only: pushing `Setup` into it leaves it in place with the violated arrow visible, and nothing beyond it moves. The all-day pair shifts by whole days and stays all-day. Dragging a terminal to close a cycle (for example `Deploy` onto `Plan`) is rejected with a transient toast. The feature has no public API yet, so the demo feeds the internal store parameters.
0 commit comments