General and Desktop

@jerin-johnson This property's default is true for buttons that have a QDialog parent; otherwise it defaults to false. https://doc.qt.io/qt-5/qpushbutton.html#autoDefault-prop Your buttonBox is a child of your QDialog, so it must be true. You can disable it manually, but then you can't accept your dialog by pressing enter anymore. But it seems that you don't need this anyway.

I finally solved this. It was due to the fact that I was building Crypto++ with MSVC2019 while Qt was built with MSVC2015

.. this solve, iam re instal msvc build tools, and copy shared folder to um..

@LorenDB @Pl45m4 is correct: "focus" is only implemented when widget is shown, it doesn't have any meaning during, say, construction. showEvent() is the earliest you should set your focus.

user interface design is a science unto itself. the widgets can do so much, but if you really want flare then plan on writing custom widgets and custom paint methods to do exactly what you're looking for.

so write a test program, meter the performance of canvas writes vs out-of-bounds writes, and report back.

Thankyou all for your help - it is working now. @Christian-Ehrlicher You put me on the right track. In another part of the application I had a bug that would reopen the file for writing !

@Cocojambo said in Load balancing between several Threads: I mean that all 4 new threads may be created in one core and we won't get any benefit of such multi threading. You can't with Qt. But the OS will for sure not put all four threads on one core and leave the other three idle when the four have something to do.

@Joerg-Brueggmann That I don't know, you probably know more than I! My understanding is that once you use any stylesheet colors they override any palettes you might set in Qt styles. That's just how it is --- stylesheets are evaluated/act after everything else.

@VRonin said in problem with QLocalSocket sending continues data to QLocalServer: This is not correct. Damn, and sorry! I thought that it had said that, but not. I may have confused with readyRead() is not emitted recursively; if you reenter the event loop or call waitForReadyRead() inside a slot connected to the readyRead() signal, the signal will not be reemitted (although waitForReadyRead() may still return true).

@chrizbee Qt does not mess up the system include paths... appending the include path or setting PATH I don't know what PATH should have to do with a compiler include path nor why I should add a default include path to my pro (or cmake) file - looks like your compiler setup is incorrect.

@rtvideo For the "not found", start from https://github.com/probonopd/linuxdeployqt/issues/350 https://github.com/probonopd/linuxdeployqt/issues/338 ? I have no idea whether those warnings are connected to your tabs issue.

@Pablo-J-Rogina @mrjj Ok, setting virtual display with Xvfb :1 -screen 0 1024x768x16 & and setting variables: ENV QT_DEBUG_PLUGINS=1 ENV QT_QPA_PLATFORM=xcb ENV QT_QPA_PLATFORM_PLUGIN_PATH=/opt/Qt/${QT_VERSION}/gcc_64/plugins ENV QT_PLUGIN_PATH=/opt/Qt/${QT_VERSION}/gcc_64/plugins ENV DISPLAY=:1 solved everything! It finally works ! :) Thanks for yours interest!

OK, so i don't know exactly why but I got it working. I believe that the following were the problems: m_udpSocket->bind(QHostAddress::AnyIPv4, 4210) **instead of** udpSocket->bind(45454, QUdpSocket::ShareAddress); as mentioned in the broadcast receiver example connect(m_udpSocket, &QUdpSocket::readyRead, this, &Receiver::processPendingDatagrams); **instead of** connect(m_udpSocket, SIGNAL(readyRead()), this, SLOT(ReceiveData()), Qt::QueuedConnection); what i used in my initial application when posting for help while (m_udpSocket->hasPendingDatagrams()) { datagram.resize(int(m_udpSocket->pendingDatagramSize())); m_udpSocket->readDatagram(datagram.data(), datagram.size()); qDebug() << "Message: " << datagram.constData(); } **instead of** while (m_udpSocket->hasPendingDatagrams()) { QByteArray datagram; QHostAddress sender; quint16 senderPort; qDebug() << "2 "; datagram.resize(m_udpSocket->pendingDatagramSize()); m_udpSocket->readDatagram(datagram.data(), datagram.size(), &sender, &senderPort); qDebug() << "Message from: " << sender.toString(); qDebug() << "Message port: " << senderPort; qDebug() << "Message: " << **datagram;** //as per my initial program } Thank you all for all your involvement and support Regards Elian N.

@VRonin hi, I run the code sucess, how to keep baseEditor always display not that I should click the mouse.

@JonB oh, sorry, didn't recognized the link, this article i've read already i work with astra linux, it has poppler and i hope that's enough for my task

Thank you very much for the quick answer. I was afraid of that.

https://bugreports.qt.io/browse/QTBUG-87735 bug fixed) Fix Version/s: 6.0.0 RC

@fkaraokur I am lost as to where you are at now. Do you have some path working where it picks up an existing database as you desire, or is it still not finding any database and is creating a new one each time? If you are saying it is working for you by putting the database into some directory like build-BIST-Desktop_Qt_5_15_1_MinGW_64_bit-Debug, you really should read what we have all said above. This is just not the right place to put a database file. For example, it won't work once you compile for Release, it won't exist if anybody but you runs the program, and if you did distribute your application read/writing a database in the same directory as the executable will at best be a bad idea and at worst be forbidden.

You have to call QSqlQuery::next() as explained in the documentation.