Hi
Currently we are blocking QtBase_dev and qt4. We need to get a fix for an
autotest through so that any commit will have a chance to pass the CI.
Also, you might have noticed a few problems in the CI with breaking builds.
Jenkins crashed and lost track of qtbase_dev and crashed a few other
I find a lot #ifdef Q_WS_* code in Qt sources (widgets).
AFAIK Q_WS_ is no longer defined due to QPA.
Is this something which has not been ported over to Q_OS_ and/or to QPA and do
I need to expect
problems (missing functionality) when I port my app from Qt4 to Qt5 ?
--
Best regards/Schöne
Since moc is unable to do safety checks for such complex expressions (in
this case, `if (ui ui-customWidget)`), this makes Q_PROPERTY
potentially unsafe and the idea has no any value to me.
Simply do s/ui-customWidget/parent()-customWidget/g and imagine what
could happen there...
P.S. @Olivier:
On Wednesday 12. March 2014 12.48.20 Olivier Goffart wrote:
On Monday 10 March 2014 17:43:35 Giuseppe D'Angelo wrote:
Can you please explain what this feature is about, why do you think
it's useful, how it's supposed to be used, etc.?
On 10 March 2014 17:30, mikhail.svet...@gmail.com
Hello,
More than one month has passed and nobody reported any regression, so is time
to move 5.2.1 to stable repository.
Cheers,
BogDan.
From: BogDan bog_dan...@yahoo.com
To: android-developm...@qt-project.org android-developm...@qt-project.org;
Hi Jerome,
On 12 March 2014 17:37, Pasion Jerome jerome.pas...@digia.com wrote:
Hello all,
Some comments:
0) We're trying to promote the latest documentation, which contains the
latest fixes. 5.3 documentation is by-and-large much better than the 5.0 or
5.1 documentation. Whichever
Em qua 12 mar 2014, às 12:23:33, Martin Koller escreveu:
I find a lot #ifdef Q_WS_* code in Qt sources (widgets).
AFAIK Q_WS_ is no longer defined due to QPA.
Is this something which has not been ported over to Q_OS_ and/or to QPA and
do I need to expect problems (missing functionality) when I
I think the syntax is not so nice especially the need to have both
the class name and the 'path' to the property.
About syntax, I think i can make syntax easier.
For example:
Q_PROPERTY(QString label ALIAS ui-customWidget-label)
or:
Q_PROPERTY(QString label ALIAS ui-customWidget label)
On 12 March 2014 11:08, Sarajärvi Tony tony.saraja...@digia.com wrote:
Hi
Currently we are blocking QtBase_dev and qt4. We need to get a fix for an
autotest through so that any commit will have a chance to pass the CI.
Also, you might have noticed a few problems in the CI with breaking
Hi,
Unfortunately the QtBluetooth module doesn't support Windows at this stage. The
officially supported 5.3 platforms for this module are Linux/Bluez 4.x, QNX and
Android.
--
Alex
From: development-bounces+alexander.blasche=digia@qt-project.org
On Wednesday, 2014-03-12, 08:10:18, Thiago Macieira wrote:
Em qua 12 mar 2014, às 12:23:33, Martin Koller escreveu:
I find a lot #ifdef Q_WS_* code in Qt sources (widgets).
AFAIK Q_WS_ is no longer defined due to QPA.
Is this something which has not been ported over to Q_OS_ and/or to QPA
On Wednesday 12 March 2014 08:10:18 Thiago Macieira wrote:
Em qua 12 mar 2014, às 12:23:33, Martin Koller escreveu:
I find a lot #ifdef Q_WS_* code in Qt sources (widgets).
AFAIK Q_WS_ is no longer defined due to QPA.
Is this something which has not been ported over to Q_OS_ and/or to QPA
Em qua 12 mar 2014, às 18:46:15, Martin Koller escreveu:
On Wednesday 12 March 2014 08:10:18 Thiago Macieira wrote:
Em qua 12 mar 2014, às 12:23:33, Martin Koller escreveu:
I find a lot #ifdef Q_WS_* code in Qt sources (widgets).
AFAIK Q_WS_ is no longer defined due to QPA.
Is this
Hi,
[Mostly notes for Andy Shaw to review, but thought I'd post for anyone
interested]
In QtPrintSupport you can set the resolution to be used in printing, but as
with many parts of painting and printing there is confusion and inconsistency
between the painting resolution and the physical
14 matches
Mail list logo
