-
Key: DD11-15
-
Legacy Issue Number: 18679
-
Status: closed
-
Source: Fraunhofer FOKUS ( Mr. Max Bureck)
-
Summary:
The description of the Canvas element does not say how attributes inherited from GraphicalElement are handled. Since the Canvas explicitly references a background color and a fill, I assume that the attributes "sharedStyle" and "localStyle" are only taken into account for calculation of an effective style of child elements. Since the canvas defines a background, I guess it should fill the parent UI control, so a clip path wouldn't make much sense. Since transforms can also be applied to the fill of an application, I guess the transforms are just applied to the group of containing children. Please clarify, if this assumptions are correct.
-
Reported: DD 1.0 — Mon, 22 Apr 2013 04:00 GMT
-
Disposition: Resolved — DD 1.1
-
Disposition Summary:
Since canvases are groups, they inherit the fact that "The (local or shared) styles defined on a group cascade to its member elements" (see Subclause 10.3.12), that is, the styles are not for the group itself (the revision below spells out the meaing of "cascade"). Conversely, canvases support background colors and fills for themselves (backgroundColor and backgroundFill), as opposed to their members.
Graphical elements, including canvases, can have clip paths applied to them to restrict painting (for example, applying an oval mask to a background). This is separate from the fact that canvases, as groups, are lower in z-order than their members and therefore appear to be additionally clipped by their members.
Fills can have transforms (Fill::transform) to change how they are applied on their graphical elements. This is separate from transforms on graphical elements (GraphicalElement:transform), which apply to graphical elements themselves. -
Updated: Fri, 6 Mar 2015 20:58 GMT
DD11 — Styling capabilities of Canvas ambiguous
- Key: DD11-15
- OMG Task Force: Diagram Definition 1.1 RTF