1. 16 Dec, 2019 1 commit
  2. 12 Dec, 2019 1 commit
  3. 10 Apr, 2018 4 commits
  4. 14 Mar, 2018 2 commits
  5. 02 Feb, 2018 4 commits
  6. 15 Jan, 2018 6 commits
  7. 20 Apr, 2017 1 commit
  8. 19 Apr, 2017 1 commit
  9. 23 Nov, 2016 2 commits
  10. 20 Nov, 2016 1 commit
  11. 18 Nov, 2016 1 commit
  12. 02 Nov, 2016 1 commit
  13. 21 Oct, 2016 1 commit
  14. 08 Oct, 2016 1 commit
  15. 24 Jun, 2016 5 commits
    • martinjones's avatar
      MER: Build on qtdeclarative 5.6 · ee43fe90
      martinjones authored
      ee43fe90
    • Alex Blasche's avatar
      Make compile QtLocation after changes to QValuePrivate · 43dc39a8
      Alex Blasche authored
      Change-Id: I0ff4814d1615226140144a6185abc793f35ebab0
      Reviewed-by: default avatarSimon Hausmann <simon.hausmann@digia.com>
      43dc39a8
    • Alex Blasche's avatar
      Remove V8 references from QtLocation · a53a8ffd
      Alex Blasche authored
      This fixes the current build break in dev too.
      
      Change-Id: Id35f4411c228e4365042ab370c7c505f611cb694
      Reviewed-by: default avatarSimon Hausmann <simon.hausmann@digia.com>
      Reviewed-by: default avatarMichal Klocek <michal.klocek@digia.com>
      a53a8ffd
    • Alex Blasche's avatar
      Make QtLocation work after internal valuetype changes in QtQML · eb9adb6d
      Alex Blasche authored
      The value type wrapper code was completely removed. Instead
      QGeoShape & derived classes and QGeoCoordinate use Q_GADGET
      to advertise their meta data which in turn allows QtQML
      to dynamically discover the types when needed.
      
      This implies that the above C++ classes become larger as the meta
      data is permanently added. On the positive side all QML value type
      wrapper were removed which reduces the QML plugin size. At the
      same time it becomes significantly easier to use those types in
      other QML plugins such as the QtLocation one.
      
      Unfortunately this change comes with an unavoidable behavior change
      as well. Previously is was possible to set a width and height
      on an invalid QML rectangle. In the case of an invalid rect it was
      made valid (setting center to 0,0) before setting the height or
      width. The QGeoRectangle class explicitly aborts calls to
      setHeight() and setWidth() in case of an invalid rect. From
      now on the C++ class behavior is used in QML too. This was
      the reason for the change to tst_map_routing.qml in this patch.
      Incidentally the documentation always referred to the QGeoRectangle
      documentation and thus always stated the now new behavior.
      
      Documentation for the value types and the relevant behavior changes
      will be re-added in a later commit.
      
      Each Gadget must be registered
      using QMetaType::registerComparators<T>() to enable == and !=
      operators in QML. Unfortunately QMetaType requires the operator<
      which does not make any sense for the value types touched by
      this patch. Right now, a warning is printed. Attempts will
      be made to remove the operator< requirement in QMetaType.
      Otherwise the warning has to be removed before the release
      as they are printed very often.
      
      [ChangeLog][QtPositioning][Important Behavior Changes] The QML
      rectangle type ignores setting of the height and width if the
      rectangle is invalid. Previously the property setter changed
      the rectangle center to QGeoCoordinate(0,0) before setting the
      height and width of a previously invalid rectangle.
      
      Change-Id: Iab98ede58066ce03b2b4e0ce03ed85ba7ecb1020
      Reviewed-by: default avatarSimon Hausmann <simon.hausmann@digia.com>
      
      Conflicts:
      	src/imports/location/qdeclarativegeoroute.cpp
      	src/imports/location/qdeclarativegeoroutemodel.cpp
      	src/imports/location/qdeclarativegeoroutesegment.cpp
      	src/imports/location/qdeclarativepolygonmapitem.cpp
      	src/imports/location/qdeclarativepolylinemapitem.cpp
      	src/imports/positioning/locationvaluetypeprovider.cpp
      	src/imports/positioning/locationvaluetypeprovider.h
      	src/imports/positioning/positioning.cpp
      	src/imports/positioning/qdeclarativecoordinate.cpp
      	src/imports/positioning/qdeclarativecoordinate_p.h
      	src/imports/positioning/qdeclarativegeocircle.cpp
      	src/imports/positioning/qdeclarativegeocircle.h
      	src/imports/positioning/qdeclarativegeorectangle.cpp
      	src/imports/positioning/qdeclarativegeorectangle.h
      	src/imports/positioning/qdeclarativegeoshape.cpp
      	src/imports/positioning/qdeclarativegeoshape.h
      	src/positioning/qgeocircle.cpp
      	src/positioning/qgeocircle.h
      	src/positioning/qgeocoordinate.h
      	src/positioning/qgeorectangle.cpp
      	src/positioning/qgeorectangle.h
      	src/positioning/qgeoshape.cpp
      	src/positioning/qgeoshape.h
      	tests/auto/declarative_core/tst_map_routing.qml
      	tests/auto/qgeocoordinate/tst_qgeocoordinate.cpp
      eb9adb6d
    • martinjones's avatar
  16. 11 Jun, 2016 1 commit
  17. 04 Jun, 2016 1 commit
  18. 19 May, 2016 1 commit
    • chriadam's avatar
      Merge branch 'jb34945' into 'mer-stable' · 742ed879
      chriadam authored
      [QtLocation] Use Qt event loop to emit signals from GLib callbacks. Contributes to JB#34945
      
      This commit ensures that we use Qt::QueuedConnection to emit signals
      (or invoke functions which emit signals) within codepaths which are
      entered from the glib event loop, to avoid QTBUG-18434.
      
      Contributes to JB#34945
      
      See merge request !4
      742ed879
  19. 03 May, 2016 1 commit
  20. 04 Mar, 2016 2 commits
  21. 02 Jul, 2015 2 commits