Originally, I have proposed that patch in response to a question on
StackOverflow on non-intuitive Dialog behaviour. I thought it was just a
bug fix, and didn't check if QtWidgets behave differently.
If such change is not suitable for Qt 5.x, then, I'd like to suggest a
property that disables auto
-clang_developer-build_OSX_10.9/log.txt.gz
Any idea why? The tests fails on Linux my machine as well, but in different
QVERIFY().
Best,
Oleg
On Tue, Oct 7, 2014 at 10:07 AM, Joerg Bornemann <
joerg.bornem...@theqtcompany.com> wrote:
> On 07-Oct-14 18:21, Oleg Shparber wrote:
>
>
Hi,
I cannot get my changes [1] through CI for qtdeclarative/5.4. Originally it
failed with qquickwindow tests, but now it does not compile on Windows CE
platform.
Can anyone take a look at the situation?
1. https://codereview.qt-project.org/96314
Best,
Oleg
Gerrit has become terribly slow, I cannot view pull requests or files. It
fails with 502 gateway error sometimes.
Thanks,
Oleg
On Fri, Jun 13, 2014 at 12:44 AM, Haataja Ismo
wrote:
> Hi,
>
>
>
> Deployment was successful, thanks for your patience.
>
>
>
> If you find any problems, please let
Hi all,
During development of the QtQuick2 application for BlackBerry 10 I noticed
that all lists scrolls very quite slow. Same thing with any move of
Flickable's content. The reason is the high resolution of the device's
display.
The problem is that there are constants which predefine behaviour
Being a 3rd party observer and thoroughly reading all messages by Tuukkla I
anyway cannot understand the logic behind having 4.8.3-1 version instead of
suggested 4.8.4 with new copyrights, MinGW and SSL fixes.
What is wrong with releasing it right now and then process all the new
commits since 4.8.
