General and Desktop

Well, my best advice is keep an eye on it, if it causes trouble in the future then revisit the issue. I couldn't spot anything obvious in the code itself, and it disappearing with a different version of the same compiler probably means it's some peculiarity of the linkage that's probably irrelevant.

@JonB Thx. Issue closed. QEventLoop works for me. Here example.

Hi, QScrollArea is your friend :-)

@dzungng QTableWidget inherits from QTableView. That means all QTableView methods are also available on a QTableWidget. This principle is worth understanding, as it applies all over the place with QWidgets (and other Qt derived classes).

Hi, Thanks for sharing your findings !

@Belfix How is your question related to this thread?

@stdave I'm not sure I understand the problem. You add more widgets to the layout using addWidget(). Or what is the problem?

Yep, it's in my bookmarks :) Maybe the only helpful discussion about this protocol. There is an open source implementation, which tries to encode/decode but written with .Net. Further features can be observed from that project but first, I need to be able to communicate over IP layer. This will be a new Transport Layer protocol hence not implemented in Qt. Still struggling to find a way in the QUdpSocket implementation in qtcore source package. My next shot will be system socket libraries or boost::asio.

Hi and welcome to devnet, You have the details of their handling in QUIP15

Hi, You have to explicitly install it. That module was deprecated a long time ago.

From (very old) memory, it think the one having issues was OS X.

Can you reproduce that with a minimal example ? If it only happens in Plasma, you may have unearthed an issue there.

@JulienMaille said in processEvent() differs between Qt4 and Qt5: My question targets processEvent() not Qxt I'm using QxtSignalWaiter to wait synchronously for a signal, with no issues and, as stated in another topic here, it worked fine until Qt5.9/5.10. Then it started to get stuck in the processEvent() call and generate other erratic behaviors. mhhh... anyway: fix your code and make it async.

@Wapiti said in QProcess emit exit signal too earlier: QString launcher = "C:/Program Files/D-BOX/Gaming/Assetto Corsa/ACWithLiveMotion.exe"; QProcess process; connect(&process, SIGNAL(finished(int , QProcess::ExitStatus )), this, SLOT(SessionFinish())); process.start(launcher, QStringList()); void MainWindow::SessionFinish() { qDebug() << "session is finish"; } Are you sure that you did not use local variable? if process is defined in the header, the connection should look like this? connect(process, SIGNAL(finished(int , QProcess::ExitStatus )), this, SLOT(SessionFinish()));

I went as far as editing QVTKRenderWindowInteractor.py that ships with VTK. The original file is using either QWidget or QGLWidget as its base class, default being QWidget. I changed it to use QOpenGLWidget. I tried with the 3 different base classes: exact same behavior.