[Cleanup/Debug Logs] Use Q_FUNC_INFO in many more places.

[nephros]

Make debug info and include guard match source file/function names

[piggz]

Thanks! ... could you use Q_FUNC_INFO instead of strings ... i generally do this nowadays :)

[nephros]

Good point, I'll do some more of those.

[nephros]

Well, went all over the place with these. Hope this is acceptable.

[jmlich]

In general, I like that change and I like having function name in the log. However, there is a generic way to do that.
The function myMessageOutput can be adjusted to provide all the details.

harbour-amazfish/daemon/src/harbour-amazfish-daemon.cpp

Lines 25 to 30 in d5e3fe6

	void myMessageOutput(QtMsgType type, const QMessageLogContext &context, const QString &msg)
	{
	QByteArray localMsg = msg.toLocal8Bit();
	const char* time = QDateTime::currentDateTime().toString("yyyy-MM-dd hh:mm:ss.zzz").toLocal8Bit();
	fprintf(stderr, "%s : %s\n", time, localMsg.constData());
	}

I am using that in few projects, for example:
https://github.com/jmlich/geotagging/blob/a332aa865e0e4eae655fa8f998bc63c8ba4a089a/main.cpp#L9-L82

It have some pitfalls, e.g. QT_MESSAGELOGCONTEXT define and some compiler flag must be used, otherwise filename and line is removed.

[nephros]

The function myMessageOutput [...]

I'm not sure I understand right. Is this a request to switch all qDebug() (and friends) to this custom method?

I could do that of course, but I wouldn't be comfortable doing that without approval from the original code authors/maintainers.

[jmlich]

Its not request, it maybe suggestion or opening of discussion. As I said previously, I am more less fine with keeping it same as you made it.

[piggz]

Ill accept this for now ... ive used the myMessageHandler approach in the past, and maybe something to do as a next step?