1. 24 Oct, 2016 - 2 commits
  2. 18 Oct, 2016 - 1 commit
  3. 07 Oct, 2016 - 1 commit
  4. 06 Oct, 2016 - 4 commits
  5. 05 Oct, 2016 - 3 commits
    • Frederik Gladhorn's avatar
      Fix panActive state when last touch point is released · 0624390e
      Frederik Gladhorn authored
      
      When a touch interaction ends, the map would only consider the number of
      points, not their state. Thus when pan was active, it would always stay
      active, because in the release event, the number of points is still at
      least one.
      
      This also requires a reset of the synthetic mouse point, since otherwise the mouse
      point will be copied into the list of touch points, preventing the
      number of points to ever go down to zero.
      
      Change-Id: I9821d09d75f883d01eb38b741e2b5658036be334
      Reviewed-by: default avatarPaolo Angelelli <paolo.angelelli@qt.io>
      0624390e
    • Frederik Gladhorn's avatar
      QDeclarativeGeoMapItemBase::childMouseEventFilter: Do not eat release events · bfba4efe
      Frederik Gladhorn authored
      
      The filter can lead to events outside of the item being "dismissed" or
      rather sent the the map item.  When testing with MapRects, when dragging
      a map rect fast, I would sometimes get release events outside of the map
      rect, which would then end up being deliverd to the
      QDeclarativeGeopMapItemBase subclass. This effectively prevents
      MouseAreas inside of the GeoMapItem from receiving their release event.
      That in turn breaks follow up events to said items.
      
      While I still consider this extremely evil and bad behavior, at least
      this doesn't completely break event delivery any more.
      
      Change-Id: I228d64e04140e2434779d07d8f03a8e9f2d11f83
      Reviewed-by: default avatarPaolo Angelelli <paolo.angelelli@qt.io>
      bfba4efe
    • Paolo Angelelli's avatar
      Fix cache mixing with high-dpi and low-dpi osm providers · 218e208b
      Paolo Angelelli authored
      
      This cache fixes the cache mixing problem that has been introduced
      with the osm high dpi tiles support.
      
      high dpi providers fall back to low dpi ones and ultimately
      to hardcoded providers (also low dpi), and can also be enabled/disabled
      via plugin parameter, thus leaving the cache for a given map id
      dirty for the next run.
      
      With this patch high dpi tiles are named differently from low dpi ones.
      If high-dpi providers are selected, but become not available, the
      cache can also change the tileset to load at runtime
      
      Change-Id: I229692da07c1fc61c58fb0b6fae6ec5af16e43a7
      Reviewed-by: default avatarPaolo Angelelli <paolo.angelelli@qt.io>
      218e208b
  6. 04 Oct, 2016 - 1 commit
    • Frederik Gladhorn's avatar
      Remove a bunch of ungrabTouch/Mouse calls · a65d9b7a
      Frederik Gladhorn authored
      
      Ungrabbing means actively not wanting to receive any future events.
      With slight changes in the event delivery in Qt 5.8, this leads to
      release events not being delivered to the items, which in turn means
      that the map thinks it's pressed after the last touch is gone.
      
      There is no reason to call ungrab at all, when an event ends in a
      regular way (release/cancel). The only reason to ungrab is when for some
      reason future move/release events are unwanted, in which case the item
      needs to make sure it's in the right state (as in not expecting release
      events to follow).
      
      Task-number: QTBUG-56213
      Change-Id: Ieb8dbf4d8ab312cff461c4fe8a3621af67a132b9
      Reviewed-by: default avatarPaolo Angelelli <paolo.angelelli@theqtcompany.com>
      Reviewed-by: default avatarShawn Rutledge <shawn.rutledge@qt.io>
      a65d9b7a
  7. 03 Oct, 2016 - 3 commits
  8. 29 Sep, 2016 - 1 commit
  9. 26 Sep, 2016 - 1 commit
  10. 23 Sep, 2016 - 1 commit
    • Paolo Angelelli's avatar
      Document licenses of Qt Location · 573171bd
      Paolo Angelelli authored
      
      Add qt_attribution.json files for 3rdparty code in Qt Location, and
      list the attributions in the index file. Also document the different
      licenses the module is available under as a whole.
      
      The _legal.qdoc files apparently weren't included anywhere, and have
      been removed.
      
      Change-Id: I56e8b75ae044954c745b2fde6f7cd4c1e80ec1b3
      Reviewed-by: default avatarAlex Blasche <alexander.blasche@qt.io>
      573171bd
  11. 21 Sep, 2016 - 2 commits
  12. 19 Sep, 2016 - 1 commit
  13. 18 Sep, 2016 - 1 commit
  14. 17 Sep, 2016 - 1 commit
  15. 16 Sep, 2016 - 1 commit
  16. 15 Sep, 2016 - 1 commit
  17. 14 Sep, 2016 - 1 commit
  18. 12 Sep, 2016 - 1 commit
  19. 05 Sep, 2016 - 1 commit
  20. 31 Aug, 2016 - 1 commit
  21. 30 Aug, 2016 - 2 commits
    • Paolo Angelelli's avatar
      OSM: Honor min/max zoom level limits coming from the provider records · ee4bbb76
      Paolo Angelelli authored
      
      This patch prevents the tile fetcher from requesting tiles with a
      z values that is outside the range defined in the provider record.
      If the provider record does not specify these values, the default
      values are used (0 and 20)
      
      Change-Id: I5c3f7be8bbd2b2ce6c8c8d6d8d81431237e60f5b
      Reviewed-by: default avatarAlex Blasche <alexander.blasche@qt.io>
      ee4bbb76
    • Paolo Angelelli's avatar
      Add OSM plugin parameter osm.mapping.highdpi_tiles · 52c8bfa6
      Paolo Angelelli authored
      
      This patch adds a mean to enable/disable high dpi support for the
      OSM plugin too, following the same approach taken for the mapbox and
      here plugins.
      
      In order to do so, it has been necessary to rework QGeoTileProviderOsm.
      It can now be constructed with an arbitrary number of TileProviders,
      as opposed to the previous approach with one primary and one fallback
      tileprovider.
      
      It has also been necessary to disable Nearest interpolation for high
      dpi tiles, as it appears to produce considerable artifacts.
      So in presence of highdpi tiles, Linear interpolation is now always
      used.
      
      Change-Id: Id7d20fd5a320f3d5ef41b9fa28447a5c4f5398be
      Reviewed-by: default avatarAlex Blasche <alexander.blasche@qt.io>
      52c8bfa6
  22. 29 Aug, 2016 - 1 commit
  23. 26 Aug, 2016 - 4 commits
  24. 22 Aug, 2016 - 2 commits
  25. 18 Aug, 2016 - 2 commits