Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-71960

Qml Map Error doesn't update when QGeoServiceProvider gets a ConnectionError

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • P3: Somewhat important
    • None
    • 5.9.1
    • Location
    • None
    • Linux (Debian) - Qt 5.9.1

    • Linux/Other display system

    Description

      Hi,

      I'm currently developing my own geoservices plugin and I cannot get a connectionError signal in my qml file. 

      Let me explain my context :

      I'm having my own mapServer generating tiles. My app allow the user to change the background map. So I'm using the same mechanism that the osm Plugin. Only one plugin, having multiples mapTypes, but mapTypes are all coming from my server. Sometimes, it can happen that my server falls. If so, it will restart, but the current port could still be busy. It will then restart on an other port. 

      If so, my child class QGeoServiceProvider will emit the tileError signal. Unfortunately I cannot catch this signal in the map qml element.

      I'd like to catch it to inform the app that the server falls and to get the new address, and then destroy and recreate the map qml with the new address.

      It seems that the map properties Error and ErrorString are set in the QDeclarativeGeoMap:: PluginReady using the provider values.

      Also if I referred to the Qml documentation for Map QML type, the error and errorString properties are describe as the last error occurred in the provider. In my plugin I only fill them in the pluginReady method and I can't find where to catch them properly.

      Is there a way to make this connection in my plugin ? 

      Thanks

       

       

       

       

       

      Attachments

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

        Activity

          People

            paangele Paolo Angelelli
            valerie Valérie Basson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes