I again saw qDebugs committed with Q_FUNC_INFO explicitely in them, which
shows that yes, the default should be changed :-)
On Thursday 29 March 2012 17:02:38 Olivier Goffart wrote:
> On Thursday 29 March 2012 13:17:14 kai.koe...@nokia.com wrote:
> > For my original proposal I took inspiration fr
On Thursday 29 March 2012 13:17:14 kai.koe...@nokia.com wrote:
> For my original proposal I took inspiration from the KDE debug output.
> Anyhow, I agree that the application name / pid just adds noise if you
> launched your app yourself from the shell.
>
> So, about "[%{type}] %{function} - %{me
> -Original Message-
> From: Ramsay Lincoln (Nokia-MP/Brisbane)
> Sent: Thursday, March 29, 2012 9:20 AM
> To: Koehne Kai (Nokia-MP/Berlin)
> Cc: development@qt-project.org
> Subject: Re: [Development] Proposal: Changing the default output of
> qDebug and friends
>
On 03/29/2012 05:03 PM, Koehne Kai (Nokia-MP/Berlin) wrote:
>> Why can't Creator just set the QT_MESSAGE_PATTERN environment
>> variable then and leave the default alone? Creator would not need
>> to show the filename and line number, just use them for when you
>> click on the warnings.
>
> You're
.org
> Subject: Re: [Development] Proposal: Changing the default output of
> qDebug and friends
>
> On 03/29/2012 12:39 AM, ext kai.koe...@nokia.com wrote:
> > PS: From an IDE perspective including the file + line would help so
> > that you could just 'jump' to th
On Thursday 29 March 2012 10:02:59 Lincoln Ramsay wrote:
> On 03/29/2012 09:54 AM, ext Olivier Goffart wrote:
> > That would be possible with runtime backtrace (#include
> > backtrace(), on Linux)
> > So one could add some tokens in QT_MESSAGE_PATTERN to get the backtrace.
> > The problem is that r
On 03/29/2012 09:54 AM, ext Olivier Goffart wrote:
> That would be possible with runtime backtrace (#include
> backtrace(), on Linux)
> So one could add some tokens in QT_MESSAGE_PATTERN to get the backtrace.
> The problem is that runtime backtrace is often not really accurate.
Getting a whole bac
On Thursday 29 March 2012 09:43:53 Lincoln Ramsay wrote:
> On 03/29/2012 09:41 AM, ext Lincoln Ramsay wrote:
> > Why can't Creator just set the QT_MESSAGE_PATTERN environment variable
> > then and leave the default alone? Creator would not need to show the
> > filename and line number, just use the
On 03/29/2012 09:41 AM, ext Lincoln Ramsay wrote:
> Why can't Creator just set the QT_MESSAGE_PATTERN environment variable
> then and leave the default alone? Creator would not need to show the
> filename and line number, just use them for when you click on the warnings.
And related to this...
If
On 03/29/2012 12:39 AM, ext kai.koe...@nokia.com wrote:
> PS: From an IDE perspective including the file + line would help so
> that you could just 'jump' to the source of a warning by clicking on
> it. However, the file string can get quite long (think about shadow
> builds) ...
Why can't Creator
Hi there,
In Qt 4 qDebug, qWarning etc just printed whatever was passed in. In Qt 5 we've
been changing this (1) so that you can configure Qt to print additional
information by setting the QT_MESSAGE_PATTERN environment variable. However, we
didn't change the default so far - so without setting
11 matches
Mail list logo
