Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for WebAssembly
  4. How to disable dialog.exec() warning?
Forum Updated to NodeBB v4.3 + New Features

How to disable dialog.exec() warning?

Scheduled Pinned Locked Moved Unsolved Qt for WebAssembly
3 Posts 2 Posters 451 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W Offline
    W Offline
    wenqing zhong
    wrote on 8 May 2022, 05:28 last edited by wenqing zhong 5 Aug 2022, 05:29
    #1

    I am using 6.3 with asyncify, the dialog.exec() run normally, but when the dialog is open, the browser console prompt the warning message below continueously. it is difficault to debug other things. Is there any way to stop prompt the messages?

    Warning: dialog exec() is not supported on Qt for WebAssembly in this configuration. Please use show() instead, or enable experimental support for asyncify.
    qtloader.js:396 When using exec() (without asyncify) the dialog will show, the user can interact with it and the appropriate signals will be emitted on close. However, the exec() call never returns, stack content at the time of the exec() call is leaked, and the exec() call may interfere with input event processing

    1 Reply Last reply
    0
    • L Offline
      L Offline
      lorn.potter
      wrote on 16 May 2022, 06:39 last edited by
      #2

      That message will not show for ayncify configurations.

      It is ifdef'd out by the #ifndef QT_HAVE_EMSCRIPTEN_ASYNCIFY
      Did you configure Qt with -device-option QT_EMSCRIPTEN_ASYNCIFY=1 and rebuild?

      If you are seeing that message, you probably have not configured qt to use asyncify.

      Freelance Software Engineer, Platform Maintainer QtWebAssembly, Maintainer QtSensors
      Author, Hands-On Mobile and Embedded Development with Qt 5 http://bit.ly/HandsOnMobileEmbedded

      W 1 Reply Last reply 16 May 2022, 13:04
      0
      • L lorn.potter
        16 May 2022, 06:39

        That message will not show for ayncify configurations.

        It is ifdef'd out by the #ifndef QT_HAVE_EMSCRIPTEN_ASYNCIFY
        Did you configure Qt with -device-option QT_EMSCRIPTEN_ASYNCIFY=1 and rebuild?

        If you are seeing that message, you probably have not configured qt to use asyncify.

        W Offline
        W Offline
        wenqing zhong
        wrote on 16 May 2022, 13:04 last edited by
        #3

        @lorn-potter Yes, I rebuild QT with the below configure., and thread and asyncify work well.

        configure -no-warnings-are-errors -qt-host-path e:/qt/6.3.0/mingw_64 -xplatform wasm-emscripten -nomake examples -feature-thread -device-option QT_EMSCRIPTEN_ASYNCIFY=1 -prefix e:/Qt/6.3.0/wasm_async

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved