On Tuesday, 20 August 2019 14:46:57 PDT Konstantin Tokarev wrote:
> 21.08.2019, 00:45, "Thiago Macieira" :
> > I'd like to propose we announce now that it will not be supported for Qt
> > 5.15.
> >
> > Even if 2019 still has code generation problems.
>
> Does it mean that you recommend using
21.08.2019, 00:45, "Thiago Macieira" :
> I'd like to propose we announce now that it will not be supported for Qt 5.15.
>
> Even if 2019 still has code generation problems.
Does it mean that you recommend using 2015 instead?
> We should assume that MS will
> fix them soon.
>
> --
> Thiago
I'd like to propose we announce now that it will not be supported for Qt 5.15.
Even if 2019 still has code generation problems. We should assume that MS will
fix them soon.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel System Software Products
On Tuesday, 20 August 2019 14:25:27 PDT Philippe wrote:
> > There's no mutex.
>
> On Visual Studio 2017 15.8.8,
That's a broken compiler, a regression from 2015 and fixed on 2019. Try *any*
other compiler and you'll see there's no mutex.
Same bug that makes static with VS 2017 crash on start.
> There's no mutex.
On Visual Studio 2017 15.8.8, there is a mutex on the 1st call
(checked today when step tracing the assembly code).
Again, for block scope, that is:
void foo()
{
QString s = QStringLiteral("abc");
...
}
Philippe
On Tue, 20 Aug 2019 14:11:59 -0700
Thiago
On Tuesday, 20 August 2019 08:56:06 PDT Bogdan Vatra via Development wrote:
> Isn't silly to have so many wrappers around a such a simple thing as
> strings?
We all wish it were simple. If it were, we would have no need for so many
string classes, for Marc's email and even for SG16 (Unicode)
On Tuesday, 20 August 2019 03:41:45 PDT Philippe wrote:
> another Drawback : it causes a global mutex to be executed on first use
> inside a block scope (c++11 static variable thread safety).
There's no mutex.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel
On Tuesday, 20 August 2019 03:04:12 PDT Mutz, Marc via Development wrote:
> - You can use u"..." in Qt sources unconditionally
>- converts implicitly to QStringView
And you can use UTF-8 text there[*], since all our compilers now support UTF-8
and are configured to parse it.
[*] untested
Fabrice Mousset (20 August 2019 18:05)
> I've got this issue when qtquickcompiler is enabled!
> When I remove qtquickcompiler, it works!
Please file a bug report against the qtquickcompiler,
Eddy.
___
Development mailing list
Hi all,
I am **modernizing** our application from Qt 5.4.2 to last LTS version (Qt
5.12.4).
I have a problem which I can't understand and needs some help.
I have declared a QQuickPaintedItem object which has an enumeration to defined
drawing types, like this:
class TourPlayerItem : public
Hi,
Isn't silly to have so many wrappers around a such a simple thing as
strings? All the major frameworks out there (i.e. Java, C#) they have a single
String which does all the magic.
In Qt we have: QString, lost of QString::fromXXX, QLatin1String,
QStringLiteral, QStringView, QByteArray
On 17/08/2019 00.13, Sze Howe Koh wrote:
> QLabel returns some CoW types by-pointer as a legacy from Qt 1 times [1]:
>
> QPixmap *QLabel::pixmap() const;
> QPixture *QLabel::pixmap() const;
Does this allow one to obtain the internal pixmap and modify it in-place
without then calling
I and Kari Oikarinen created an epic, some user stories, and further
some sub-tasks what needs to be done related to C++17 usage in Qt 6.
The link to the epic, under from which you can navigate to the more
detailed levels, is here:
https://bugreports.qt.io/browse/QTBUG-77477
Feedback,
Hi,
Initial ones here:
https://codereview.qt-project.org/q/message:%2522Add+changes+file+for+Qt+5.12.5%2522
Maintainers, please do needed modifications & make sure changes will be
approved during this week.
br,
Jani Heikkinen
Release Manager
___
another Drawback : it causes a global mutex to be executed on first use
inside a block scope (c++11 static variable thread safety).
Philippe
On Tue, 20 Aug 2019 12:04:12 +0200
"Mutz, Marc via Development" wrote:
> Hi,
>
> In light of a recent attempt to re-introduce QStringLiteral, relacing
Hi,
In light of a recent attempt to re-introduce QStringLiteral, relacing
QLatin1String, I'd like to remind everyone that QStringLiteral has a lot
of drawbacks and should not be used unless it saves a memory allocation.
Drawbacks include:
- doubled storage requirements (2 bytes/char) over a
On Mon, Aug 19, 2019 at 1:04 PM Volker Hilsheimer
wrote:
>
> On 19 Aug 2019, at 11:41, coroberti . wrote:
>
> Hi,
> Could be this issue be given a priority since it's a regression
> and strikes deployments of Qt-5.12 LTS on Windows?
>
> https://bugreports.qt.io/browse/QTBUG-44096
>
>
>
> Hey
Repository has been created as requested.
- Paul
From: Development on behalf of Andy
Nichols
Date: Wednesday, 14 August 2019 at 12:24
To: "development@qt-project.org"
Subject: [Development] Repo request for Qt Quick 3D module
Hello everyone,
As The Qt Company announced today on our blog,
18 matches
Mail list logo
