1. 17 Sep, 2020 2 commits
    • Volker Krause's avatar
      Rewrite tracking of OSM data across clipping · 75fe1f3d
      Volker Krause authored
      The previous approach put coordinate pointers into the point structures of
      the clipper lib. This worked in most cases, but as there are no guarantees
      on point references remaining valid, the clipper lib ended up swapping
      values of points in some cases, breaking our coordinate references and
      subsequently losing the attached OSM data. While this is usually not a
      problem for a random node, it could also happen on the closing node of a
      polygon, causing it to no longer be closed and confusing the hell out of
      the geometry reassembly code.
      The new approach tracks this outside of the clipper lib with a map on the
      integer coordinates (and thus avoiding floating point number comparison
      issues). This also allows us to roll back a bunch of Marble-specific
      changes to the clipper code.
    • Volker Krause's avatar
      Update clipper code to 6.4.2 from upstream · 73c4289d
      Volker Krause authored
  2. 15 Sep, 2020 1 commit
  3. 10 Sep, 2020 3 commits
  4. 01 Sep, 2020 1 commit
  5. 31 Aug, 2020 6 commits
  6. 28 Aug, 2020 1 commit
  7. 15 Aug, 2020 6 commits
  8. 08 Aug, 2020 1 commit
  9. 05 Aug, 2020 3 commits
  10. 02 Aug, 2020 15 commits
  11. 01 Aug, 2020 1 commit
    • Johnny Jazeix's avatar
      Fix Windows build. · 952eac8b
      Johnny Jazeix authored
      QT_STRICT_ITERATORS do not work on vs compilers.
      Missing ZLib includes for osm runner plugin.