Opened 12 years ago
Last modified 12 years ago
#4272 new defect
Order of lines in symbol definition matters!
Reported by: | woodbri | Owned by: | sdlime |
---|---|---|---|
Priority: | normal | Milestone: | 6.2 release |
Component: | MapServer C Library | Version: | svn-trunk (development) |
Severity: | normal | Keywords: | |
Cc: |
Description
The order of the lines in a symbol definition matters where the symbol is displayable when referenced and this should not be the case.
This symbol is good and displays:
symbol name "S" type svg image '/u/data/tiger2011-maps/etc/svg/hwy/S-blank.svg' end
This symbol does not generate an error but it will not display the symbol when it is later referenced for use:
symbol name "S" image '/u/data/tiger2011-maps/etc/svg/hwy/S-blank.svg' type svg end
In general, in the mapfile the order of the object attributes does not matter. In fact the ONLY case I am aware of is the fact LAYER TYPE must be defined before a FEATURE object is defined. We should avoid creating more cases like this.
Note:
See TracTickets
for help on using tickets.
This is probably also related to #4271