During the testing, we've found a bunch of bugs and other issues. I'd
suggest uploading this WIP branch to codereview, like we do for any other
stuff.
Regards,
Konstantin
2013/12/21 Mark Gaiser
> On Fri, Dec 6, 2013 at 4:11 PM, Mitch Curtis
> wrote:
> > On 12/06/2013 03:08 PM, Mark Gaiser wro
Hi all,
I'm trying to compile qt-5.2.0 on arch linux, but with/without
icu-support I get the following error:
make[3]: Entering directory
'/usr/local/src/qt-everywhere-opensource-src-5.2.0/qtbase/src/platformsupport'
LD_LIBRARY_PATH=/usr/local/src/qt-everywhere-opensource-src-5.2.0/qtbase/lib${LD
On Fri, Dec 6, 2013 at 4:11 PM, Mitch Curtis wrote:
> On 12/06/2013 03:08 PM, Mark Gaiser wrote:
>>
>> On Fri, Dec 6, 2013 at 2:02 PM, Mitch Curtis
>> wrote:
>>>
>>> Hello.
>>>
>>> At the beginning of this year I started work on a Calendar for Qt Quick
>>> Controls as a sort of side project. Afte
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,
On further consideration, I also recommend that the open and close methods
in QQmlWebSocket be public Q_INVOKABLE and any open/close testing logic in
setUrl be moved to the open and close methods, reducing the need for
additional error handling in the setUrl method. I also don't understand why
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
