Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Virtual keyboard do not show when debug build.
Forum Updated to NodeBB v4.3 + New Features

Virtual keyboard do not show when debug build.

Scheduled Pinned Locked Moved Unsolved General and Desktop
3 Posts 2 Posters 445 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.
  • Crawl.WC Offline
    Crawl.WC Offline
    Crawl.W
    wrote on last edited by
    #1

    This cause happens when build with vs+add-on and qtcreator+msvc both at Qt5.12. Even the program will crash when I use "start debugging" with QtCreator. I confirm that it cause by virtual keyboard because I comment out qputenv("QT_IM_MODULE", QByteArray("qtvirtualkeyboard")); with everything is ok, and virtual keyboard do not show when debug build refers to this. My code as following:

    int main(int argc, char *argv[])
    {
        QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
        qputenv("QT_IM_MODULE", QByteArray("qtvirtualkeyboard"));
        //    QCoreApplication::setAttribute(Qt::AA_UseOpenGLES);
    
        QApplication app(argc, argv);
    
        //OTHER CODE
    
        return app.exec();
    }
    

    This is dependency graph of program when debug build and haven't dependency about virtual keyboard.
    0_1557287882966_004a54dc-de7a-4555-9097-92ebdab6b0c5-image.png

    jsulmJ 1 Reply Last reply
    0
    • Crawl.WC Crawl.W

      This cause happens when build with vs+add-on and qtcreator+msvc both at Qt5.12. Even the program will crash when I use "start debugging" with QtCreator. I confirm that it cause by virtual keyboard because I comment out qputenv("QT_IM_MODULE", QByteArray("qtvirtualkeyboard")); with everything is ok, and virtual keyboard do not show when debug build refers to this. My code as following:

      int main(int argc, char *argv[])
      {
          QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
          qputenv("QT_IM_MODULE", QByteArray("qtvirtualkeyboard"));
          //    QCoreApplication::setAttribute(Qt::AA_UseOpenGLES);
      
          QApplication app(argc, argv);
      
          //OTHER CODE
      
          return app.exec();
      }
      

      This is dependency graph of program when debug build and haven't dependency about virtual keyboard.
      0_1557287882966_004a54dc-de7a-4555-9097-92ebdab6b0c5-image.png

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @Crawl.W said in Virtual keyboard do not show when debug build.:

      Even the program will crash when I use "start debugging" with QtCreator.

      Do you have stack trace after the crash?

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      Crawl.WC 1 Reply Last reply
      0
      • jsulmJ jsulm

        @Crawl.W said in Virtual keyboard do not show when debug build.:

        Even the program will crash when I use "start debugging" with QtCreator.

        Do you have stack trace after the crash?

        Crawl.WC Offline
        Crawl.WC Offline
        Crawl.W
        wrote on last edited by
        #3

        @jsulm Yes,it's disassembler result, can not see something. Whole stack trace as following graph:
        0_1557293694444_fcf7c6f5-0838-45e5-bfdc-053492d9755c-image.png

        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