diff --git a/docs/userguide/en/applications/apps-icon-o-matic.html b/docs/userguide/en/applications/apps-icon-o-matic.html index 144cfecc6e..f8f5aff2ee 100644 --- a/docs/userguide/en/applications/apps-icon-o-matic.html +++ b/docs/userguide/en/applications/apps-icon-o-matic.html @@ -244,7 +244,7 @@ width="64" height="64" />

See how there are no numbers in the 16px version of the BeVexed icon? That's done with the "Level of Detail" setting of their shapes.
With the LOD you control the visibility of a shape depending on its size. That way, you can leave away details of an icon that looks good on a bigger icon, but maybe not so much on its smaller version.

-

This is how it works: A LOD of 1.0 is defined as a 64px icon size. So, to get the LOD of a particular icon size you simply divide it by 64, e.g. a 16px icon has a LOD of 16/64 = 0,25. A shape won't be visible below its Min LOD and above its Max LOD.

+

This is how it works: A LOD of 1.0 is defined as a 64px icon size. So, to get the LOD of a particular icon size you simply divide it by 64, e.g. a 16px icon has a LOD of 16/64 = 0.25. A shape won't be visible below its Min LOD and above its Max LOD.

So, if you set a shape's Min LOD to 0.0 and the Max LOD to 0.5, this means that the shape will only be visible for icon sizes smaller or equal to 32px. If you wanted to exclude the 32px icon size, you'd have to stay below 0.5, say 0.49.

The LOD is not only for leaving out detailing shapes, you can also use it to e.g. change the stroke width at different sizes, if you feel that's needed. Simply duplicate a shape, make your changes and set both of their LOD settings to show either one or the other. Here lies the only source of potential confusion, when you're unwittingly overlap LODs of shapes, and wonder why at some size both are visible...
For example, if Shape 1 were to be shown below 48px and Shape 2 from 48px upward (LOD: 48/64 = 0.75):