| commit | 9d13968c212a33a700e527a3124c5555eee4fa2d | |
| author | Nicola Fontana <ntd@entidi.it> | |
| Fri, 20 Jan 2017 14:45:51 +0000 (20 15:45 +0100) | ||
| committer | Nicola Fontana <ntd@entidi.it> | |
| Fri, 20 Jan 2017 14:48:19 +0000 (20 15:48 +0100) | ||
| tree | 90da2380833410fe46d0d941059f6c5c6d597e3b | treesnapshot (tar.gz zip) |
| parent | 0d073b29cbe1e61fe6bae4588d49926383e924e1 | commitdiff |
adg: add floating entity concept and API
When an entity is "floating", its extents does not concur on increasing
the extents of its own container. In other words, during the arrange
phase AdgContainer only considers the non-floating children to compute
its extents.
In particular, this affects how adg_canvas_autoscale() works: all
floating entities are not taken into consideration.
A typical example is the title block or any other annotation not
dependent from the model for positioning.
When an entity is "floating", its extents does not concur on increasing
the extents of its own container. In other words, during the arrange
phase AdgContainer only considers the non-floating children to compute
its extents.
In particular, this affects how adg_canvas_autoscale() works: all
floating entities are not taken into consideration.
A typical example is the title block or any other annotation not
dependent from the model for positioning.