Behalf Of Andreas Aardal Hanssen
> Sent: Tuesday, December 24, 2013 1:38 AM
> To: development@qt-project.org
> Subject: Re: [Development] [Request] Add Info to QDebug
>
> On 23 Dec 2013, at 21:39, Kurt Pattyn wrote:
>
> On 23 Dec 2013, at 17:38, development-requ...@qt-projec
On 23 Dec 2013, at 21:39, Kurt Pattyn wrote:
> On 23 Dec 2013, at 17:38, development-requ...@qt-project.org wrote:
>> From: Andreas Aardal Hanssen
>> Subject: Re: [Development] [Request] Add Info to QDebug
>> Date: 23 Dec 2013 15:17:06 GMT+1
>> To: development
On 23 Dec 2013, at 17:38, development-requ...@qt-project.org wrote:
> From: Andreas Aardal Hanssen
> Subject: Re: [Development] [Request] Add Info to QDebug
> Date: 23 Dec 2013 15:17:06 GMT+1
> To: development@qt-project.org
>
> FTR, I’m completely -1 for touching QDebug a
On segunda-feira, 23 de dezembro de 2013 08:05:18, Keith Gardner wrote:
> I believe that regardless of the outcome for qError, I think the addition
> of a qInfo would be greatly welcomed. I would like to present to the user
> some runtime information that is not intended for debugging but could be
On 23 Dec 2013, at 14:42, Thiago Macieira wrote:
>> Fatal conditions affect not only the application, but also the surrounding
>> system. The application and possibly the whole system should be shutdown
>> immediately. A good example is loss of control of an X-ray beam in an X-ray
>> scanner. Even
On Mon, Dec 23, 2013 at 7:42 AM, Thiago Macieira
wrote:
> On segunda-feira, 23 de dezembro de 2013 14:06:07, Kurt Pattyn wrote:
> > > - Warning: is a notice that something went wrong, but it might not
> affect
> > > the application. You can disable it with QT_NO_WARNING_OUTPUT since is
> > > not t
On segunda-feira, 23 de dezembro de 2013 14:06:07, Kurt Pattyn wrote:
> > - Warning: is a notice that something went wrong, but it might not affect
> > the application. You can disable it with QT_NO_WARNING_OUTPUT since is
> > not that important.
>
> Warnings are not errors, and do not require imm
On 23 Dec 2013, at 12:00, development-requ...@qt-project.org wrote:
> From: Alejandro Exojo
> Subject: Re: [Development] [Request] Add Info to QDebug
> Date: 22 Dec 2013 19:01:51 GMT+1
> To: development@qt-project.org
>
>
> El Saturday 21 December 2013, Kurt Pattyn escr
El Saturday 21 December 2013, Kurt Pattyn escribió:
> Qt currently supports the following ‘severity’ levels for logging: Debug,
> Warning, Critical, Fatal and System.
>
> I propose to add the following levels: Info and Error, with associated
> methods qInfo() and qError(). Particularly, the Info s
On 22 Dec 2013, at 05:51, development-requ...@qt-project.org wrote:
> From: Thiago Macieira
> Subject: Re: [Development] [Request] Add Info to QDebug
> Date: 21 Dec 2013 17:15:20 GMT+1
> To: development@qt-project.org
>
>
> On sábado, 21 de dezembro de 2013 14:23:10, Kur
On sábado, 21 de dezembro de 2013 14:23:10, Kurt Pattyn wrote:
> Qt currently supports the following ‘severity’ levels for logging: Debug,
> Warning, Critical, Fatal and System.
>
> I propose to add the following levels: Info and Error, with associated
> methods qInfo() and qError(). Particularly,
Qt currently supports the following ‘severity’ levels for logging: Debug,
Warning, Critical, Fatal and System.
I propose to add the following levels: Info and Error, with associated methods
qInfo() and qError().
Particularly, the Info severity can be interesting to have applications output
log
12 matches
Mail list logo
