Changeset 886 in josm for trunk/styles/standard
- Timestamp:
- 2008-08-28T22:51:31+02:00 (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/styles/standard/elemstyles.xml
r885 r886 1 1 <!-- 2 alittle help:2 A little help: 3 3 1. every rule starts with <rule> and ends with </rule> 4 4 2. every rule needs a condition … … 6 6 -v for the value as a string 7 7 -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! 9 10 3. line attributes 10 11 - width absolute width in pixel in every zoom level 11 12 - realwidth relative width which will be scaled in meters, integer 12 13 - colour 13 4. area attributes 14 - priority 15 4. 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. 23 5. area attributes 14 24 - 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 26 6. icon attributes 27 - icon path to icon, relative to the icon path (default: where this file is) 28 - priority 29 7. scale_min / scale_max 30 - zoom scale for display 31 32 Using both area and line attributes for the same key/value pair does work. For areas 33 first the rbest matching area rule is searched and the best matching line rule is 34 connected with it. They need not have the same key/value pair. 20 35 21 36 The colours can consist of the two components - name and hex code (e.g. water#0000ff). 22 37 If both are given, the color name is introduced in preferences with that value. If only 23 38 code 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! 39 modified preferences or previous value is used. The color code can also have a hex value 40 containing the alpha channel (thus havin 8 hex digits instead of 6). 41 42 If a key/value pair matches more than one rule, the "rule that wins" is unpredicted 43 in case they have same priority! Using priority settings helps to solve conflicts. 27 44 --> 28 45
Note:
See TracChangeset
for help on using the changeset viewer.