Hi Gerd I've looked through all the places I could find that took [highPrec]coord vals, manipulated them and then converted back and they all seem safe with my patch.
There might be slight differences where, using Java2DConverter or similar, a calculated value converts to a different/adjacent highPrec value from the old code; I don't think this matters. Original values will be restored to the same highPrec value. I'll try and remember not to use +ve and -ve; it is very common shorthand in English Ticker On Sat, 2023-10-07 at 07:07 +0000, Gerd Petermann wrote: > Hi Ticker, > > I did some tests and your patch really seems to solve the problem without > introducing new ones > :) > > Just one remark: Please try to avoid terms like "+ve" in javadoc. I had to > read this > two times to understand that it means positive ;) > > So, if you don't find furher things to change I would be happy to commit the > patch, although I > don't yet understand > why it also fixes the MP gaps issue. > > Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
