Found it: https://github.com/qt/qtbase/blob/5.12/src/corelib/global/qlogging.cpp

Specifically, I needed to set application name in QCoreApplication.

Hi.

Initially we were thinking of creating plugin. Then we found out that people uses various IDE's when developing several platforms/systems and idea was dropped.

Now the typical work flow is that you code using your favorite IDE and on second screen you have analysis running without stepping into way.

What comes to Qt, we implemented small logging library that does basic stuff and OS level CPU and Memory usage logging. It might be good idea to check latest Qt logging API and support for those as well.

Kind regards,
Erkki Salonen
Tampere
Finland

Since the obvious answer to the question is a resounding 'no', I'll mark this question as 'solved', although I'll still have to think about a way to achieve what we want in the most convenient way.

Hi and welcome to devnet,

Do you have by any change QT_FATAL_WARNINGS defined ?

If not, can you try the same thing with the 5.6 beta ?

Hi @AnantAgrawal,

Just just launch your app from the console. qDebug, qWarning etc. will be printed to the console too (stdout/stderr). Make sure you don't define QT_NO_DEBUG_OUTPUT -- see http://doc.qt.io/qt-5/debug.html for more info.

Hi and welcome to devnet,

One thing in you code is that in your receive function your are looping over each byte you received and ask to update the widget. What is generally done when handling large amount of data in such small amount is that the processing is done in a different thread. Also the UI update should be batched, there's no real benefit to update your QPlainTextEdit content for every single byte you get.

Hope it helps

Hi Rahul,

I am looking something similar i.e. logs of Qt framework. Refer https://forum.qt.io/topic/58566/how-to-print-logs-qdebug-qwarning-qcritical-qfatal-of-qt-framework-libraries-itself

Try using --log-level=0. It might work in your case.

Thanks,
Anant Agrawal

@JR You're welcome :) Personally I neither had any experience in writing iOS apps nor have the necessary hardware/keys/certificates for that. So any input on the subject will be useful (but I doubt that it will be possible to make any enhancements based on that).