Techniques
Crossings — gaps, bridges and square jumps
How disconnected lines cross: a gap, a rounded jump, or a local square jump — the mark that says "not connected".
ddn@1New DDN source
Why use it?
A crossing misread as a junction is a defect that ships; the crossing mark is the honest "no connection here".
When it helps
Any routed diagram where unrelated lines must cross — bus layouts, networks, wiring.
How to read it
- Find the crossing: the mark (gap, bridge or square) belongs to the line that hops, and it means exactly one thing.
- Connected lines join at a node; crossed lines pass — the mark removes the ambiguity.
- The router minimizes crossings first (optimize: crossings is the default and keeps improving); the mark disambiguates the crossings that remain, it does not excuse a tangled layout.
What you need
- The model
- The crossing style declaration
Things to check
- Do not rely on colour alone to separate crossing lines — marks survive print and colour-blindness.
- One crossing style per diagram; mixed marks reintroduce the ambiguity.
Scope of this diagram
Crossing marks are presentation disambiguation; connectivity is declared in the model, never inferred from geometry.
Work with the converted example
- Open the viewer and select
crossing_gap. Inspect the rendered view and its source. - Open the designer. Keep the selected profile and inspect its legal palette and property controls.
- Change one displayed title or an appropriate data value. Apply the edit and check the resulting diagram.
- Run the verifier and review its diagnostics before moving complete content into review.
- Download your edited DDN source to retain the change.
The example uses the indentation-based ddn-next-1 dialect. The language guide explains reusable definitions, dotted data rows and explicit property blocks.