diff options
| author | Sebastian Geerken <devnull@localhost> | 2015-01-23 17:22:07 +0100 |
|---|---|---|
| committer | Sebastian Geerken <devnull@localhost> | 2015-01-23 17:22:07 +0100 |
| commit | 9d17539aa2d7c7b00ae08cdd0615ff6ea84493fc (patch) | |
| tree | 78af7a02bbbec9b38cd44871f073abcff82f8a87 | |
| parent | 157c44928d2d4d08ba9f18742290bdd6ba229d12 (diff) | |
Interrupted drawing: more documentation.
| -rw-r--r-- | doc/dw-interrupted-drawing.doc | 16 |
1 files changed, 13 insertions, 3 deletions
diff --git a/doc/dw-interrupted-drawing.doc b/doc/dw-interrupted-drawing.doc index cb84ec8b..4da3b8c3 100644 --- a/doc/dw-interrupted-drawing.doc +++ b/doc/dw-interrupted-drawing.doc @@ -88,9 +88,19 @@ The exact control flow is described in this sequence diagram: When is drawing interrupted? ============================ -A widget holding references to widgets out of flow (which are not -necessary children) draws them as interruption if ... TODO. See -dw::oof::OOFAwareWidget::doesWidgetOOFInterruptDrawing. +A widget out of flow is regarded as part of the stacking context (see +\ref dw-stacking-context) of its *generator* (in the example above: +#fl-1 is part of the stacking context stablished by #sc-1, not the one +established by body). For this reason, a widget out of flow must, in +some cases, drawn while the *gerator* is drawn, as an +interruption. The exact rule: + +A widget out of flow must be drawn as an interruption (while the +*generator* is drawn) if the stacking context of the generator (to +which this widget belongs) is in front of the stacking context of the +container (the parent widget). + +See dw::oof::OOFAwareWidget::doesWidgetOOFInterruptDrawing. How does interruption of drawing work? |