On Friday, 22 November 2019 20:01:30 CET Giuseppe D'Angelo via Development
wrote:
> Il 22/11/19 18:49, Thiago Macieira ha scritto:
> > We decided not to add q6sizetype. Just add a "### Qt6: qsizetype" comment
> > where you can't use qsizetype in Qt 6. We'll deal with conflicts.
>
> Sorry, what
Am 22.11.19 um 17:03 schrieb Kai Köhne:
From: Development On Behalf Of
Joerg Bornemann
On 11/22/19 7:21 AM, Kai Pastor, DG0YT wrote:
Given the Qt Creator example, would it be feasible to make explicit
declaration of a file's context mandatory, at least for the existing
("fast") parser? If not
Il 22/11/19 18:49, Thiago Macieira ha scritto:
We decided not to add q6sizetype. Just add a "### Qt6: qsizetype" comment
where you can't use qsizetype in Qt 6. We'll deal with conflicts.
Sorry, what do you mean by "conflicts"? I mean that there's countless
code today that uses "int s =
Am 22.11.2019 um 15:18 schrieb Timur Pocheptsov:
Before moving to QtNetwork it needs to be significantly refactored
Can we maybe create a sub-task for this to elaborate what's meant with
'significantly refactored'?
Thx,
Christian
___
Development
On Fri, Nov 22, 2019 at 03:01:25PM +0100, Uwe Rathmann wrote:
> On 11/22/19 11:01 AM, Friedemann Kleint wrote:
>
> > https://wiki.qt.io/Qt_Contributors_Summit_2019_Qt_6_Changes_/_Migration
>
> Maybe one aspect I would like to add: there is a lot of software, that has
> to be compilable with Qt 5
On Fri, Nov 22, 2019 at 04:19:21PM +, Kai Koehne wrote:
Anyhow, QCommandLineParser processes command line arguments from the
outside. These command line arguments might come from other tools,
output ... so it should be really robust in handling these.
"from the outside" is not the
Il 21/11/19 13:13, Robert Loehning ha scritto:
>> ** [https://doc.qt.io/qt-5/qregularexpression.html QRegularExpression]
Giuseppe D'Angelo (22 November 2019 18:17) replied:
> This should mostly be fuzzing libpcre itself...
... which Google is probably already doing.
> Note that users should
On Friday, 22 November 2019 18:04:22 CET Giuseppe D'Angelo via Development
wrote:
> So the mandatory question is: how many warnings is this going to cause,
> and how to port code whilst maintaining Qt 5 compatibility?
We decided not to add q6sizetype. Just add a "### Qt6: qsizetype" comment
Hello Giuseppe,
>> qmlRegisterSingletonInstance("Utils", 3, 14, "Obj", obj);
>In 5.14 the solution is something along the lines of
Exactly what I was looking for.
>In pre-5.14 the same is achieved by using qmlRegisterSingletonType with
>a callback (that returns the object + sets the ownership of
Il 21/11/19 13:13, Robert Loehning ha scritto:
** [https://doc.qt.io/qt-5/qregularexpression.html QRegularExpression]
This should mostly be fuzzing libpcre itself...
Note that users should NEVER use / accept untrusted regular expressions.
While we shouldn't crash or exhaust memory, PCREs
Il 22/11/19 16:49, Damian Ivanov ha scritto:
I don't see this anywhere documented how this could be done using a singleton.
In 5.14 the solution is something along the lines of
qmlRegisterSingletonInstance("Utils", 3, 14, "Obj", obj);
then in QML
import Utils 3.14
// use "Obj" instead of
Additionally
https://forum.qt.io/topic/54353/solved-access-qml-singleton-object-from-c-code/4
seems also like a viable solution
though a syntax where qmlRegisterSingletonType return value is a
QObject would be very ease to read / write.
On Fri, Nov 22, 2019 at 6:33 PM Damian Ivanov wrote:
>
>
Il 22/11/19 18:00, Thiago Macieira ha scritto:
We didn't discuss because it's a given that we will do that. :-)
So the mandatory question is: how many warnings is this going to cause,
and how to port code whilst maintaining Qt 5 compatibility?
Thanks,
--
Giuseppe D'Angelo |
On Friday, 22 November 2019 16:43:16 CET Giuseppe D'Angelo via Development
wrote:
> Spawning a subthread since we didn't discuss this at all...
>
> Are the plans still to make the containers' size_type qsizetype?
We didn't discuss because it's a given that we will do that. :-)
Lars's patchset
Hi Dmitriy,
Well I can't seem to find an easy example but an easy example:
Instantiating a .qml with QQmlComponent::create which is of Window (I
do this for others as well) type
from c++ than I set obj->properties from c++ based on various events.
Creating a singleton class seems like adding 30
Hi Damian,
that seems to be an interesting case. Could you provide an example of why
would you need such a pattern?
Why the other way round -- creating a C++ singleton and exposing it to QML
-- doesn't work for you? That should be easier and more transparent.
Cheers
Dmitriy
On Fri, Nov 22,
> -Original Message-
> From: Development On Behalf Of
> Oswald Buddenhagen
> Sent: Thursday, November 21, 2019 2:41 PM
> To: development@qt-project.org
> Subject: Re: [Development] QtCS2019 Notes from "Fuzzing Qt" BoF session
>
> On Thu, Nov 21, 2019 at 12:13:55PM +, Robert Loehning
> -Original Message-
> From: Development On Behalf Of
> Joerg Bornemann
> Sent: Friday, November 22, 2019 1:25 PM
> To: Kai Pastor, DG0YT ; development@qt-project.org
> Subject: Re: [Development] QtCS2019 Notes: Clang-based cpp parser for
> lupdate
>
> On 11/22/19 7:21 AM, Kai Pastor,
Andre Hartmann (20 November 2019 13:30) wrote:
> I have two additions:
>
> * Reactivate the QDoc bot to sanity check the docs
> * Improve the output of sanity bot, especially for new users:
> https://bugreports.qt.io/browse/QTQAINFRA-1478
Added: Nils's write-up has now become
How would .qml files that are singletons and instantiated from c++ be used
currently I do this and am able to access it from qml and c++
QQmlComponent* component = new QQmlComponent(application_engine,
"qrc:/Component.qml");
QObject* obj = component->create();
obj->setParent(this);
Il 21/11/19 19:48, Giuseppe D'Angelo via Development ha scritto:
Written here:
https://wiki.qt.io/Qt_Contributor_Summit_2019_-_QtCore
Spawning a subthread since we didn't discuss this at all...
Are the plans still to make the containers' size_type qsizetype?
Thanks,
--
Giuseppe D'Angelo |
> these are my notes for "Code Review: Sharing the load" session, extended
> by "Improve the contributor experience of the Qt project"
Thanks for that - duly wikified at
https://wiki.qt.io/Code_Review:_Sharing_the_load
Eddy.
___
Development
I'll update wiki using this on Monday, thanks.
Best regards,
Timur.
From: Development on behalf of Maurice
Kalinowski
Sent: Thursday, November 21, 2019 8:52 AM
To: development@qt-project.org
Subject: [Development] QtCS19 Notes: Qt 6 Network Overview
Hi,
On Thursday, 21 November 2019 19:48:03 CET Giuseppe D'Angelo via Development
wrote:
> Written here:
> > https://wiki.qt.io/Qt_Contributor_Summit_2019_-_QtCore
>
> Thanks,
Thanks Peppe
* What does Qt assume on locale on UNIX systems?
** What happens if you haven't set anything?
*** Thiago:
Hi,
Il 22/11/19 11:01, Friedemann Kleint ha scritto:
at
https://wiki.qt.io/Qt_Contributors_Summit_2019_Qt_6_Changes_/_Migration
I think a clarification is in order: many of the things listed in those
notes have also been discussed in other ad-hoc sessions (QtCore,
QMetaType, etc.), and
On 11/22/19 11:01 AM, Friedemann Kleint wrote:
https://wiki.qt.io/Qt_Contributors_Summit_2019_Qt_6_Changes_/_Migration
Maybe one aspect I would like to add: there is a lot of software, that
has to be compilable with Qt 5 and Qt 6. Especially when your product is
library you can't decide
Jani,
Could you please ensure that those change log reviews have proper reviewers
added? Those reviewers should be the devs who we expect the change file to fill
with content.
--
Alex
From: Development on behalf of Jani
Heikkinen
Sent: Tuesday, 19
Hi,
This is a follow-up on what was discussed in the (second part of the) QtCore
session in the QtCS.
Lars and others have been mentioning that they dislike implicit conversions
within QVariant. Creating a new class (QAny) has been suggested, that would be
like QVariant but without the
On 11/22/19 7:21 AM, Kai Pastor, DG0YT wrote:
> Am 21.11.19 um 20:23 schrieb André Pönitz:
>> On Thu, Nov 21, 2019 at 07:48:41PM +0100, Oswald Buddenhagen wrote:
>>> a more radical and much simpler approach would be switching to gettext
>> The most prominent difference is the (usually) per-class
Hi,
> these are the notes on the QtQml session:
> Versioning
> --
>
> Once we get rid of unqualified lookups we don't need any QML versioning
> anymore. At least the minor version will become optional already in 5.15
> for well-behaved QML documents. In QML 3 it won't be allowed.
While
at https://wiki.qt.io/Qt_Contributors_Summit_2019_Qt_Solutions
--
Friedemann Kleint
The Qt Company GmbH
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
at
https://wiki.qt.io/Qt_Contributors_Summit_2019_Qt_6_Changes_/_Migration
--
Friedemann Kleint
The Qt Company GmbH
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
at https://wiki.qt.io/Qt_Contributors_Summit_2019_HighDpi
--
Friedemann Kleint
The Qt Company GmbH
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
33 matches
Mail list logo
