[mkgmap-dev] oneway=reverse handling broken.

Fri Jan 22 16:10:54 GMT 2010

Hi Felix

> See below for an example that does not work. It works with 1497, but
> 1498 breaks it.
> highway=* & copy=99 & mtb:scale:uphill!=5 & mtb:scale:uphill!=4 { set
> dontadd=yes; set taxi=no; set dontadd=oneway; set mkgmap:unpaved=1 }
> [0x10711 resolution 21 continue with_actions] *output*

Revision 1498 didn't change anything to do with continue or oneway as far
as I can tell.  You are just discovering the problem with the styles
on trunk that the actions are run in an arbitary order.  Although you
can work around that to get something that sort of works, any
change at all in the code is likely to break the workarounds, because
the actions will now run in a different order.  This doesn't happen on
the style branch (or if it did it would be a bug).

I am certain that r1498 would not have changed the way your rules
worked with the strict ordering as on the style branch
(except perhaps for performance, but that could be fixed).

So what I will do is revert 1498 on trunk and then put the patch in to
the style branch instead.  Is that OK?  Once the style branch is
merged and settled you should never have to spend so much time
changing your rules again.

Regards,

..Steve