On Thursday, 29 August 2019 05:20:48 PDT Roland Hughes wrote: > This is the architectural flaw of requiring all things GUI to occur in > the main event loop. I haven't dug into the Chrome code, but what you > describe is each tab/pane/whatever executes in its own thread doing > whatever GUI thing it needs so quite honestly it doesn't care when the > thread for the main application blocks as it continues merrily on its way. > > Until we can do all things GUI in other threads, you're hosed. > > Your only other option (and it might be a catastrophe) is to make your > parent/mainwindow/enclosing application its own QApplication of whatever > flavor and have it launch another QApplication in its own thread for > everything visible inside of the decorated frame. I've never tried it, > just a thought which occurred to me before I had even one swallow of Mt. > Dew this morning.
Replace "thread" with "process" and it correctly matches what Chrome does and what would work on Qt. You cannot start another QApplication in another thread in the same process. And that's also not what Chrome does. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
