It's worth pointing out that using the qInstallMsgHandler() approach probably slows down your app, and is otherwise more heavy on resources than the slogger2 approach which now appears standard.
Among the advantages of the slogger2 approach:
1. Writes to RAM disk (/dev/shmem/slogger2) so it's much faster in that respect and saves wear and tear on the flash storage.
2. Less impact on CPU load.
3. Reduced latency compared to what is probably a relatively heavy hit from the fflush() calls.
4. Output persists between invocations of the app, so you don't risk losing the output after a crash when you re-start the application.
5. Can probably leave your logging code in place even in production builds (as a result of all these things).
6. Built-in timestamping (to the millisecond).
7. "slog2info -w" provides continuous output across invocations, whereas "tail -f" has to be restarted with each launch. (This advantage is mainly for those who would manually do "tail -f logs/log" via SSH. Momentics basically does that for you.)
8. Easier combined log output when running two connected apps while testing Invocation Framework code.
There are probably other advantages. My point is, at least consider switching rather than unthinkingly sticking with the old console output just because it's more familiar to you.
