Uploaded image for project: 'Qt Mobility'
  1. Qt Mobility
  2. QTMOBILITY-2075

QGeoMapObject is forced to mercator on addMapObject

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Reported
    • Priority: Not Evaluated
    • Resolution: Unresolved
    • Affects Version/s: 1.2.0
    • Fix Version/s: None
    • Component/s: Location
    • Labels:
      None
    • Environment:
      QtSDK 1.2 in Windows 7 64-bit

      Description

      When using a custom Maps API plugin with it's own coordinate system, the QGraphicsGeoMap::addMapObject places the object into a strange position.

      The plugin contains a QGeoTiledMapData subclass, which is used by QGeoTiledMappingManagerEngine. The following virtual methods is implemented on the subclass.

      coordinateToWorldReferencePosition(const QGeoCoordinate& coord)
      worldReferencePositionToCoordinate(const QPoint& pixel)

      These methods provide the conversion into a certain coordinate system.

      When the map object is added via QGraphicsGeoMap::addMapObject(), it seems that the object's position is somehow forced to mercator.

      When using Qt Mobility version 1.1.3, the same code works perfectly and this does not happen.

      When debugging the situation in version 1.2.0, the parameter QPoint& pixel in the method worldReferencePositionToCoordinate() is different than in 1.1.3.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jacob Jaakko Mutikainen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:

                Gerrit Reviews

                There are no open Gerrit changes