On Tuesday, 9 July 2019 04:21:20 -03 Arnaud Clere wrote:
> I know. I was thinking aloud about using the future std::u8string... which
> presumably exhibits a std::string-like API to which Qt users would not be
> accustomed... I am not advocating for using it.
It won't be called "u8string", it will
On Tuesday, 9 July 2019 12:18:53 -03 NIkolai Marchenko wrote:
> No, we want to completely forego the qt way of storing settings.
> Fully custom class that won't interact with qsettings and won't have
> qvarianthash behind the storage.
Unlikely then.
--
Thiago Macieira - thiago.macieira (AT) inte
No, we want to completely forego the qt way of storing settings.
Fully custom class that won't interact with qsettings and won't have
qvarianthash behind the storage.
On Tue, Jul 9, 2019 at 6:16 PM Konstantin Tokarev wrote:
>
>
> 09.07.2019, 18:12, "NIkolai Marchenko" :
> > We (at our company) r
09.07.2019, 18:12, "NIkolai Marchenko" :
> We (at our company) realy, REALLY don't like qsettings for a multitude of
> reasons but are forced to deal with it because the details of how UI types
> are saved are hidden deep in the qt's implementation and are subject to any
> kind of changes qt w
We (at our company) realy, REALLY don't like qsettings for a multitude of
reasons but are forced to deal with it because the details of how UI types
are saved are hidden deep in the qt's implementation and are subject to any
kind of changes qt wants.
What we would really like is to have functions
Hi Qt Developers,
Coin production has been updated v1.1.0 -> 1.1.1
If you want to see the what has been changed in comparison to the
previous **baseline version, you can take a look at our newly
auto-generated change logs:
https://testresults.qt.io/coin/doc/changelog.html
** If you see let
> -Original Message-
> From: Thiago Macieira
> > On Monday, 8 July 2019 12:42:51 -03 Arnaud Clere wrote:
> > > -Original Message-
> > > From: Thiago Macieira
> > >
> > > I am not completely convinced of the benefit of adding of an owning UTF-8
> > > string class, though I very
> AFAIK Gatis is working on this (see
> https://bugreports.qt.io/browse/QTBUG-69414 ). There is a magic define
I have currently postponed that work. The goal is to move all auto tests that
rely on mouse to DEFINES += QTEST_QPA_MOUSE_HANDLING. Here is an example of
before vs after: https://cod
