Re: [Development] QTestlib: how not to test mouseMoveEvent handling

2019-07-10 Thread Jason McDonald
On Tue, Jul 9, 2019 at 1:39 AM Shawn Rutledge wrote: > > On 8 Jul 2019, at 16:24, Volker Hilsheimer wrote: > > > > Hi, > > > > Executive summary: > > > > * QTest::mouseMove seems to be broken > > * when simulating QEvent::MouseMove events by constructing event objects, > > always construct them

Re: [Development] char8_t summary?

2019-07-10 Thread Thiago Macieira
On Wednesday, 10 July 2019 22:01:04 -03 Thiago Macieira wrote: > On Wednesday, 10 July 2019 09:55:02 -03 André Pönitz wrote: > > As far as I understand there's a perceived need to have "full" utf8 > > literals, and there's a need to have ASCII literals. First could be > > served by some QUtf8*, sec

Re: [Development] char8_t summary?

2019-07-10 Thread Thiago Macieira
On Wednesday, 10 July 2019 09:55:02 -03 André Pönitz wrote: > As far as I understand there's a perceived need to have "full" utf8 > literals, and there's a need to have ASCII literals. First could be > served by some QUtf8*, second by QAscii*, both additions, no need to > change QLatin* semantics.

Re: [Development] char8_t summary?

2019-07-10 Thread Matthew Woehlke
On 10/07/2019 09.10, Mutz, Marc via Development wrote: > The other reason is about error checking: What should the result be of > putting an æ into a QAsciiString? Assert at runtime? UB? In > QLatin1String, this error just can't happen. Even if you feed it UTF-8, > you may get mojibake, because you

[Development] Looks like code.qt.io is down!

2019-07-10 Thread Konstantin Podsvirov
The code.qt.io at 34.244.34.65 hase not response. -- Regards, Konstantin Podsvirov ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Oslo, we have a problem [char8_t]

2019-07-10 Thread Ville Voutilainen
On Sat, 6 Jul 2019 at 19:24, Mutz, Marc via Development wrote: > > Though, if the compilers are implementing the behaviour correctly, > > maybe the right course of action is to actually complain to the > > committee that their change breaks code… > > AFAIU, this is a conscious break. See http://

Re: [Development] char8_t summary?

2019-07-10 Thread Mutz, Marc via Development
On 2019-07-10 14:55, André Pönitz wrote: On Wed, Jul 10, 2019 at 11:29:15AM +0200, Mutz, Marc via Development wrote: On 2019-07-10 10:50, Arnaud Clere wrote: > Hi all, > > So, do I understand correctly that: > 1. QUtf8String may be required in Qt7 to solve problems due to C++2x > char8_t I woul

Re: [Development] char8_t summary?

2019-07-10 Thread André Pönitz
On Wed, Jul 10, 2019 at 11:29:15AM +0200, Mutz, Marc via Development wrote: > On 2019-07-10 10:50, Arnaud Clere wrote: > > Hi all, > > > > So, do I understand correctly that: > > 1. QUtf8String may be required in Qt7 to solve problems due to C++2x > > char8_t > > I wouldn't say required. I also d

Re: [Development] char8_t summary?

2019-07-10 Thread Mutz, Marc via Development
On 2019-07-10 10:50, Arnaud Clere wrote: Hi all, So, do I understand correctly that: 1. QUtf8String may be required in Qt7 to solve problems due to C++2x char8_t I wouldn't say required. I also don't think it needs to wait until Qt 7. Qt 7 is where we may depend on C++20 and can use char8_t

Re: [Development] char8_t summary?

2019-07-10 Thread Arnaud Clere
Hi all, So, do I understand correctly that: 1. QUtf8String may be required in Qt7 to solve problems due to C++2x char8_t 2. QByteArray methods currently operating on latin1 may be restricted to ascii in Qt6 to avoid problems when const char* input really is utf8 3. QLatin1String may become QLatin