> -Original Message-
> From: development-bounces+martin.jones=nokia@qt-project.org
> [mailto:development-bounces+martin.jones=nokia@qt-project.org]
> On Behalf Of Knoll Lars (Nokia-MP/Oslo)
> Sent: Friday, February 03, 2012 10:18 PM
> To: Ahumada Sergio (Nokia-MP/Oslo); development@
On 5.2.2012 16.12, "lars.kn...@nokia.com" wrote:
>We also need to now create a team that focuses on creating packages out of
>our source code that we can then release. For the Alpha I propose that we
>only do source packages (great if we get binaries though), we will however
>need to prepare for
That's exactly right.
Category log is not on at all at default.
If category log is on the default output is used (same of qDebug()).
Only logging in an output log file is active if you explicit set this in your
config file.
Activation of category log comes from outside via configuration file and
On Sunday 05 February 2012 10:50:48 BRM wrote:
> > From: Diego Iastrubni
> >
> >On Fri, Feb 3, 2012 at 1:10 PM, David Faure wrote:
> >
> >Once this goes in I'll add support for %pid%, %processname% and
> >%timestamp%,>
> >>and we'll be all set :)
> >
> >You meant %threadid% of course... right?
>
> From: Diego Iastrubni
>On Fri, Feb 3, 2012 at 1:10 PM, David Faure wrote:
>
>Once this goes in I'll add support for %pid%, %processname% and %timestamp%,
>>and we'll be all set :)
>
>You meant %threadid% of course... right?
Wouldn't having both available be useful?
Ben
On Fri, Feb 3, 2012 at 1:10 PM, David Faure wrote:
> Once this goes in I'll add support for %pid%, %processname% and
> %timestamp%,
> and we'll be all set :)
>
You meant %threadid% of course... right?
___
Development mailing list
Development@qt-project
On Sunday, 5 de February de 2012 17.10.55, lars.kn...@nokia.com wrote:
> Yes, so we can either go through and clean them all up at once (best,
> since it might require API changes as with QString::utf16()), or introduce
> a new name for this kind of thread safety and document which classes work
> t
On 2/5/12 4:38 PM, "ext Thiago Macieira" wrote:
>Hi all
>
>Lars's email about the feature freeze included a line about the plugin
>mechanism in Qt. I posted about this many moons ago but it's still
>unfinished.
>Thanks to Brad, it at least has stopped using QSettings to cache
>information.
>
>Ho
On 2/5/12 5:30 PM, "ext Thiago Macieira" wrote:
>Hi all
>
>During the QJsonDocument review process, I pointed out a problem with
>using
>const_cast that I argued was a violation of the thread-safety rules. Lars
>disagreed, so we talked here at FOSDEM. Strict reading of the docs at
> http:/
On 2/5/12 4:27 PM, "ext Robin Burchell" wrote:
>On Sun, Feb 5, 2012 at 3:12 PM, wrote:
>> * finish codecForCStrings & codecForTr removal (QTBUG-21872)
>
>Relatedly - but I think it probably deserves separate mention - would
>be the defaulting of passing raw bytes to QString to use utf8
>encodin
Hi all
During the QJsonDocument review process, I pointed out a problem with using
const_cast that I argued was a violation of the thread-safety rules. Lars
disagreed, so we talked here at FOSDEM. Strict reading of the docs at
http://developer.qt.nokia.com/doc/qt-4.8/threads-reentrancy.htm
Hi all
Lars's email about the feature freeze included a line about the plugin
mechanism in Qt. I posted about this many moons ago but it's still unfinished.
Thanks to Brad, it at least has stopped using QSettings to cache information.
However, we still need to get some information from the plugin
On Sun, Feb 5, 2012 at 3:12 PM, wrote:
> * finish codecForCStrings & codecForTr removal (QTBUG-21872)
Relatedly - but I think it probably deserves separate mention - would
be the defaulting of passing raw bytes to QString to use utf8
encoding. It's a little more involved, but definitely somethin
Hi everybody,
the weather in Europe seems to follow our schedule these days. It's
freezing cold.
We're now starting with our feature freeze for Qt 5. Let's go a bit
through what this means and what we need to do next.
We will soon have to start preparing the Alpha of Qt5. The purpose of the
Alph
14 matches
Mail list logo
