Anything to make one definition more specific should work. My ability to recall the full set of rules is clearly less than perfect.

So it looks like I was missing the variable statement after this. It works now. Thanks everyone for the help. QList<QObject*> list() const; for (int index=0; index < list.size(); index++) { QObject *test01 = list.value(0)->name(); qDebug() << test01; }

Qsettings documentation says it is reentrant and thread-safe but since I have started adding .sync() between writing and reading, I have not seen the problem.

try: inline QDebug operator<<(QDebug &stream, const amazing &flag) { if (!flag) { return stream << testX(0x00); } amazing l_copy = flag; testX l_bit = testX(0x01); stream.noquote().nospace() << "("; forever { if (l_copy.testFlag(l_bit)) { stream.noquote().nospace() << l_bit; l_copy.setFlag(l_bit, false); if (!l_copy) break; stream.noquote().nospace() << "|"; } l_bit = testX(qint32(l_bit) << 1); } stream.noquote().nospace() << ")"; return stream; }

Since you're explicitly calling QDebug operator<<(QDebug &stream, const base &obj) the compiler can't call the other function. What you can do is to write your own "virtual QString debug() const" function in every class which you the call within the debug stream operator function. But once again - plain C++ :)

@Dariusz your signature of the overload isn't correct: see this also make sure those implementations are in the corresponding header file

Found it: https://github.com/qt/qtbase/blob/5.12/src/corelib/global/qlogging.cpp Specifically, I needed to set application name in QCoreApplication.

@Dariusz said in qDebug overload, return non const function?: the virtual QString getDebugData never actually calls the upper inherited classes getDebugData I don't understand - what do you mean here? I don't see that you call the base class implementation in this function anywhere so how should it be called?

correct @Paul-Colby thanks

@VRonin i before write my code to this method 369 book: void WeatherBalloon::sendDatagram() { QByteArray datagram; QDataStream out(&datagram, QIODevice::WriteOnly); out.setVersion(QDataStream::Qt_4_3); out << QDateTime::currentDateTime() << temperature() << humidity() << altitude(); udpSocket.writeDatagram(datagram, QHostAddress::LocalHost, 5824); } But we want to connect UDP processing data to GUI app, it can not read QDataStream Method and it Crashs. The app is written in C#,So we should try a method that work with VisualStudio. Agian Than kyou for attention best regards stackprogramer

@kshegunov Thank you! That was the missing part!!

The reason for this is a GDB limitation on Windows. See QTCREATORBUG-24649 for more information. Regards

@JKSH Yes the value has been initialized. I init. with some minor calculations such as: QVector <double> B; for(int i=1;i<ui->RyadA->text().toInt(0,10)+1;i++){ B.push_back(((double)i/8+1)*(i+1)); }

@SGaist If there is one thing that is for sure; I can destroy any project while doing a "hello world" tutorial! Thanks for the eSupport.

@hskoglund Thanks for the info

Windows? That explains :-) I tested on Linux. I don't know how to fix this on Windows. Maybe this can help you: http://stackoverflow.com/questions/388490/unicode-characters-in-windows-command-line-how

Using QStringList.join you could achieve desired results ; QStringList list = QStringList() << "one" << "two"; qDebug().noquote() << list.join(", "); Playing around with this method quite likely gives you output you are after.

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.

qDebug().noquote() << QString("I have properly opened file %1").arg(fileName); But please... don't use non-ascii characters in source code. That's just being mean to others.

@raoulh Thank you ...

OK guys, I was able to solve the problem. The Fedora people changed a configuration file, so that qDebug output wasn't shown to the user anymore, until the user changed the settings like described here: https://bugzilla.redhat.com/show_bug.cgi?id=1227295

@_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).