Techniques
Sizing and opacity — scoped presentation overrides
Individual appearances can override eligible presentation values without replacing the underlying shared definition.
ddn@1New DDN source
Why use it?
A local display adjustment should have an explicit scope and preserve the model’s identity.
When it helps
A single oversized note in an otherwise uniform diagram, a draft node that should recede visually, a tight caption with its own shrink floor.
How to read it
- Check whether a setting belongs to the shared definition, one occurrence or the view.
- Omitted property leaves continue through the declared default hierarchy.
- Opacity changes appearance; it does not remove data from the model.
What you need
- The appearance to adjust
- Its default providers
- Applicable size and opacity properties
Things to check
- Making an item invisible is not redaction.
- Do not copy a shared definition merely to change one appearance.
Scope of this diagram
Each property follows the codex ownership and default rules; output measurement remains a separate concern.
Work with the converted example
- Open the viewer and select
main. 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.