Changeset 886 in josm for trunk/styles


Ignore:
Timestamp:
2008-08-28T22:51:31+02:00 (11 years ago)
Author:
stoecker
Message:

cleanup description

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/styles/standard/elemstyles.xml

    r885 r886  
    11<!--
    2 a little help:
     2A little help:
    331. every rule starts with <rule> and ends with </rule>
    442. every rule needs a condition
     
    66        -v for the value as a string
    77        -b for the values yes / no (boolean, will also understand true, 1 and false, 0 respectively)
    8         (although the value flags v/b for the condition are optional, using at least one of them is highly recommended!)
     8        Although the value flags v/b for the condition are optional, using at
     9        least one of them is highly recommended!
    9103. line attributes
    1011        - width absolute width in pixel in every zoom level
    1112        - realwidth relative width which will be scaled in meters, integer
    1213        - colour
    13 4. area attributes
     14        - priority
     154. linemod attributes
     16        - all line attributes
     17        - mode ('over' or 'under')
     18        - width can be specified relative to modified way:
     19          +x - <x> pixels are added to way size
     20          -x - <x> pixels are subtracted from way size
     21          x% - the size is <x> percent of modified way
     22          If the size is <= 1 the minimum size of 1 is used.
     235. area attributes
    1424        - colour
    15 5. icon attributes
    16         - icon path to icon , relative from where this file is
    17 6. scale_min / scale_max - currently unused in JOSM
    18 
    19 Using both area and line attributes for the same key/value pair doesn't work!
     25        - priority
     266. icon attributes
     27        - icon path to icon, relative to the icon path (default: where this file is)
     28        - priority
     297. scale_min / scale_max
     30        - zoom scale for display
     31
     32Using both area and line attributes for the same key/value pair does work. For areas
     33first the rbest matching area rule is searched and the best matching line rule is
     34connected with it. They need not have the same key/value pair.
    2035
    2136The colours can consist of the two components - name and hex code (e.g. water#0000ff).
    2237If both are given, the color name is introduced in preferences with that value. If only
    2338code is given (e.g. #0000ff), it is used directly. If only name is given, either user
    24 modified preferences or previous value is used.
    25 
    26 BEWARE: If a key/value pair matches more than one rule, the "rule that wins" is unpredicted!
     39modified preferences or previous value is used. The color code can also have a hex value
     40containing the alpha channel (thus havin 8 hex digits instead of 6).
     41
     42If a key/value pair matches more than one rule, the "rule that wins" is unpredicted
     43in case they have same priority! Using priority settings helps to solve conflicts.
    2744-->
    2845
Note: See TracChangeset for help on using the changeset viewer.