Hi,
AFAIK Gatis is working this (see
https://bugreports.qt.io/browse/QTBUG-69414 ). There is a magic define
widgets/widgets/qcombobox/qcombobox.pro:4:DEFINES +=
QTEST_QPA_MOUSE_HANDLING
widgets/widgets/qmenu/qmenu.pro:9: DEFINES += QTEST_QPA_MOUSE_HANDLING
which apparently changes behavior
Il 08/07/19 21:15, Иван Комиссаров ha scritto:
No, what I’ve actually meant - is it possible to have a free function that
takes some string view (QLatin1StringView?) and operates on that view instead
of allocating a new string. I’m asking because I’m kinda nooby in UTF and I
don’t really know
Hello everyone, I've been having problems with Qt3D's
FirstPersonCameraController and I was wondering if I could help
contribute to make it easier to use and more flexible.
As I see it the current problems are:
Fixed keymapDefault keys being inaccessible to some (I have no page
up/down on my l
On 8 Jul 2019, at 17:38, Shawn Rutledge
mailto:shawn.rutle...@qt.io>> wrote:
On 8 Jul 2019, at 16:24, Volker Hilsheimer
mailto:volker.hilshei...@qt.io>> wrote:
Hi,
Executive summary:
* QTest::mouseMove seems to be broken
* when simulating QEvent::MouseMove events by constructing event obje
No, what I’ve actually meant - is it possible to have a free function that
takes some string view (QLatin1StringView?) and operates on that view instead
of allocating a new string. I’m asking because I’m kinda nooby in UTF and I
don’t really know what should happen for non-ascii characters in th
On 01/07/2019 09.56, Konstantin Tokarev wrote:
> 01.07.2019, 13:30, "Ville Voutilainen" :
>> On Sat, 29 Jun 2019 at 14:34, Konstantin Tokarev wrote:
>>> Or even better: split page into "tiles" (i.e. portions of page with height
>>> of viewport) and
>>> render long page as a sequnece of tiles. T
On 30/06/2019 10.10, Holger Freyther wrote:
> On 28. Jun 2019, at 00:57, Thiago Macieira wrote:
>> In this particular case, Google loves to use Bazel. Everyone else hates that
>> they do.
>>
>> Ask anyone trying to package Tensorflow.
>
> Some Ex-Googlers like it too. It seems there is a disconne
Just checked the implementation (thanks to woboq, once again) and you're
right. These are completely unacceptable.
Konstantin
пн, 8 июл. 2019 г., 20:28 Thiago Macieira :
> On Monday, 8 July 2019 10:53:42 -03 Konstantin Ritt wrote:
> > > See my reply to Marc: users want US-ASCII case-insensitive
Den mån 8 juli 2019 kl 16:26 skrev Volker Hilsheimer :
>
> Hi,
>
> Executive summary:
>
> * QTest::mouseMove seems to be broken
> * when simulating QEvent::MouseMove events by constructing event objects,
> always construct them with global position
>
>
> The details:
>
> While trying to fix https:
On Monday, 8 July 2019 10:53:42 -03 Konstantin Ritt wrote:
> > See my reply to Marc: users want US-ASCII case-insensitive text matching
> > and
> > case folding routines, for network protocols that are US-ASCII case-
> > insensitive (DNS, IRC, etc.).
>
> That strnicmp() and std::toupper()/std::tol
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 much agree with a view over UTF-8 strings.
> > The reason is not the string
On 25/06/2019 17.53, Konrad Rosenbaum wrote:
> Option 2: put some elbow grease into QTextBrowser and make it understand
> some more tags and more CSS.
> Pros: documentation becomes visually more pleasing; minimal dependencies
> by assistant - easy to build and easy to bundle with applications;
> em
-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 much agree with a view over UTF-8 strings.
> The reason is not the string class itself (alone it is definitely useful),
> but the fact t
> 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 with global position
>
>
> The details:
>
> While trying to fix h
Hi,
Executive summary:
* QTest::mouseMove seems to be broken
* when simulating QEvent::MouseMove events by constructing event objects,
always construct them with global position
The details:
While trying to fix https://bugreports.qt.io/browse/QTBUG-76765 to not update
the mouse cursor when t
пн, 8 июл. 2019 г., 16:43 Thiago Macieira :
> On Monday, 8 July 2019 04:38:28 -03 Konstantin Ritt wrote:
> > Perhaps there is a particular reason for the user to manipulate binary
> data
> > as if it were a string? So give him that string, QString.
>
> See my reply to Marc: users want US-ASCII cas
On Monday, 8 July 2019 04:24:28 -03 Mutz, Marc via Development wrote:
> What I think when I read this is:
>
> Backed by const char*, never implicit:
> - QLatin1String - owner of L1 data [change from today, but not a
> breaking one]
> - QLatin1StringView - what QLatin1String is now [requires portin
On Monday, 8 July 2019 02:54:52 -03 Иван Комиссаров wrote:
> Is it possible to do an inplace toUpper() for the ASCII encoding?
Uh...
Q_REQUIRED_RESULT QByteArray toLower() const &
{ return toLower_helper(*this); }
Q_REQUIRED_RESULT QByteArray toLower() &&
{ return toLower_helper(*
On Monday, 8 July 2019 04:38:28 -03 Konstantin Ritt wrote:
> Perhaps there is a particular reason for the user to manipulate binary data
> as if it were a string? So give him that string, QString.
See my reply to Marc: users want US-ASCII case-insensitive text matching and
case folding routines,
On Monday, 8 July 2019 07:06:33 -03 Mutz, Marc via Development wrote:
> So no, no more inheriting of value classes from each other. QUtf8String,
> if it comes, will have to be a separate type, not a subclass of
> QByteArray.
They can be both derived from the same base, internal, common class. The
No problem Eddy, Thanks for notifying it.
On Mon, 8 Jul 2019 at 15:19, Edward Welbourne
wrote:
> Sujan Dasmahapatra (5 July 2019 20:43) asked
> > I'm loading an obj file in Qt3DWindow. The model is a restaurant which
> has many objects as sofa, table etc.
> >
> > How can I extract individual obj
Hi,
Before this gets any more traction: Aye! for QUtf8String, nay for the
implementation.
On 2019-07-08 09:46, Arnaud Clere wrote:
//! Explicitely utf8 encoded byte array
class QUtf8String : public QByteArray
{
public:
using QByteArray::QByteArray;
QUtf8String(const QByteArray& o) : Q
Sujan Dasmahapatra (5 July 2019 20:43) asked
> I'm loading an obj file in Qt3DWindow. The model is a restaurant which has
> many objects as sofa, table etc.
>
> How can I extract individual objects. I'm unable to segregate as the whole
> object is root entity.
>
> I actually want to apply texture
Arnaud Clere (8 July 2019 09:46) wrote
> Instead of asking users to choose correct QByteArray methods depending
> on the data it contains, why not proposing them to explicitly say what
> it contains?
>
> //! Explicitely utf8 encoded byte array
> class QUtf8String : public QByteArray
> {
> public:
>
Thiago had observed:
>>> Arguably, toUpper() and toLower() should be removed, since
>>>
>>> QByteArray(u8"Résumé").toLower()
>>> is mojibake.
вс, 7 июл. 2019 г., 12:58 André Hartmann
mailto:aha_1...@gmx.de>>:
>> I vote against that. If you got the "raw" data from a device as
>> described abo
On Monday, 8 July 2019 09:37:24 CEST Allan Sandfeld Jensen wrote:
> On Samstag, 6. Juli 2019 16:53:13 CEST Mutz, Marc via Development wrote:
> > On 2019-07-06 16:38, Konstantin Tokarev wrote:
> > > 06.07.2019, 17:20, "Mutz, Marc via Development"
> > >
> > > :
> > >> On 2019-07-06 14:50, Fabian Kos
On 2019-07-08 09:24, Mutz, Marc via Development wrote:
- QLatin1StringView - what QLatin1String is now [requires porting, but
it's just s/QLatin1String/QLatin1StringView/g in client code]
→ https://codereview.qt-project.org/c/qt/qtbase/+/267375
___
De
On Samstag, 6. Juli 2019 14:50:05 CEST Fabian Kosmale wrote:
> Hi,
>
> Actually, most of the time there is actually an option 3. Add yet another
> overload, this time for int. This will match the 0 literal without any
> conversion, and we can then just call the nullptr overload inside.
> Unfortuna
Hi all,
> -Original Message-
> From: Thiago Macieira
>
> But QByteArray is encoding-indeterminate since it can carry any type.
> Arguably, toUpper() and toLower() should be removed, since
> QByteArray(u8"Résumé").toLower() is mojibake.
...
> Are we willing to add ubegin() and begin8()
пн, 8 июл. 2019 г., 5:44 Thiago Macieira :
> On Sunday, 7 July 2019 23:26:40 -03 Konstantin Ritt wrote:
> > As we have string views now, I'd vote for deprecating the string
> > manipulation methods in QByteArray. I doubt we could make QByteArray a
> true
> > vector of bytes now, without breaking l
On Samstag, 6. Juli 2019 16:53:13 CEST Mutz, Marc via Development wrote:
> On 2019-07-06 16:38, Konstantin Tokarev wrote:
> > 06.07.2019, 17:20, "Mutz, Marc via Development"
> >
> > :
> >> On 2019-07-06 14:50, Fabian Kosmale wrote:
> >> [...]
> >>
> >>> See https://godbolt.org/z/e6OinY for how
On Samstag, 6. Juli 2019 12:43:39 CEST Mutz, Marc via Development wrote:
>
> Opinions?
>
I think we need separate functions anyway in order to handle our
NO_ASCII_CONVERT macros. Accepting char8_t shouldn't trigger the warning as
the encoding is well-definied.
'Allan
On 2019-07-08 04:43, Thiago Macieira wrote:
On Sunday, 7 July 2019 23:26:40 -03 Konstantin Ritt wrote:
As we have string views now, I'd vote for deprecating the string
manipulation methods in QByteArray. I doubt we could make QByteArray a
true
vector of bytes now, without breaking lots of the u
33 matches
Mail list logo
