On Mon, 18 Jan 2010, Ulf Lamping wrote:
> But this way you still need to deal with priorities to prevent yourself
> from unintended hiding of your own rules. Which I would like to avoid
> where ever possible, as this is - in my experience - often unnecessarily
> confusing :-)
I fear a better desi
Am 16.01.2010 15:34, schrieb Dirk Stöcker:
>
> You above example won't work. What I implemented was boolean AND rules:
>
>
>
>
>
>
>
> Much like conditions in XSL, ugly but it works :-)
Somehow ;-)
This prevents a multi-storey icon if the amenity is not tagged (which is
On Sat, 16 Jan 2010, Ulf Lamping wrote:
> IIRC, someone (Dirk?) said mappaint is already able to handle
> hierachical rules in elemstyles.xml, something like:
>
>
>
>
>
>
>
>
>
>
>
> So if both tags are set, the "more special multi-storey" rule will fit
> before the "more g
Hi!
IIRC, someone (Dirk?) said mappaint is already able to handle
hierachical rules in elemstyles.xml, something like:
So if both tags are set, the "more special multi-storey" rule will fit
before the "more generic parking" rule.
Using the priorities for this is
