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

QNetworkSession::waitForOpened(-1) opens a non modal dialog, allowing the user to interact with the other UI widgets. Widgets appear disabled (dimmed) when the IAP dialog is displayed but are not.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: P2: Important P2: Important
    • 1.0.2
    • 1.0.0
    • Bearer Management
    • None

      QNetworkSession::waitForOpened(-1) opens a non modal dialog, allowing the user to interact with the other UI widgets. Widgets appear disabled (dimmed) when the IAP dialog is displayed but are not disabled.

      The IAP dialog should be modal.

      Consider the following code being executed inside a custom QT dialog...

      QNetworkSession* networkSession = new QNetworkSession(cfg, this);
      networkSession->open();
      networkSession->waitForOpened(-1);

      // The IAP dialog is shown. However the user can interact with the widgets drawn behind the IAP dialog.
      // At this point the user the user closes the custom QT dialog

      int networkID = cfg.identifier().toUInt();
      doSomethingWithNetworkID(networkID);

      // The above two lines of code are never executed and networkSession is never destroyed after the user closes the containing custom QT dialog.

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

            juvuolle Juha Vuolle (closed Nokia identity) (Inactive)
            spol loughlin spollen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes