e urls to points to repos outside
of the qt/ directory.
Regards,
Benjamin Terrier
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Tue, 20 Sept 2022 at 01:34, Konstantin Ritt wrote:
> Hi Tuuka,
>
> By that link I didn't mean QTBUG-102962 exactly, but 23 matching bugs for
> a single component (which is not even one of the top-wanted components).
> On vanilla 6.2.4, QCamera simply doesn't work on many Android devices. All
>
On Wed, 13 Jul 2022 at 13:05, Florian Bruhin wrote:
>
> https://www.qt.io/product/features?hsLang=en#js-6-3 lets you see the
> individual components of Qt and what license they are available as.
>
>
That's some high level of FUD and BS.
If I select LGPLv3, all Qt tools are greyed out (moc, qmake,
On Thu, 27 May 2021 at 14:52, Allan Sandfeld Jensen
wrote:
>
> Most of the changes to signal form are not that simple, and requires a lot
> more work. Not even sure we will manage to deal with the mess that is
> acceptNavigationRequest before feature freeze.
It's easy, if you force users to use
On Thu, 27 May 2021 at 14:17, Allan Sandfeld Jensen
wrote:
> On Donnerstag, 27. Mai 2021 13:55:01 CEST Benjamin TERRIER wrote:
> > On Thu, 27 May 2021 at 11:25, Allan Sandfeld Jensen
> >
> > But then in my code, each time I see a CrazySSLPage I am never sure that
> it
&g
On Thu, 27 May 2021 at 11:25, Allan Sandfeld Jensen
wrote:
>
> I am not sure I see a significant difference. They are both compile-time.
> A
> "user" of your widget could also derive it and override the virtual
> function
> just as well as they could override your the signals?
>
>
>
No, they are
Hi,
I just saw this ticket: https://bugreports.qt.io/browse/QTBUG-74587
and this related gerrit change:
https://codereview.qt-project.org/c/qt/qtwebengine/+/346723
I am not sure what to think about it.
Sure it is nice to be able to customize a QWebEnginePage without deriving
from it, but turning
On Fri, 21 May 2021 at 14:32, Joerg Bornemann wrote:
> On 5/21/21 12:41 PM, Benjamin TERRIER wrote:
>
> > And now:
> > - all new modules and supported platforms are Commercial/GPLv3 only.
>
> Which is very different from commercial-only.
>
Please don't cut ha
On Thu, 20 May 2021 at 17:18, Jason H wrote:
>
> Anyway, these issues aren't insurmountable, apparently they can be changed
> with the stroke of a pen. (Where is Qt's Open Governance? - still think I
> misunderstood what that was about)
Since TQC alone can decide that the Qt Project won't relea
On Thu, 14 Jan 2021 at 08:21, Nibedit Dey wrote:
> Thank you everyone for the suggestions.
> I posted in the development group as there was less participation on the
> topic in the interest group.
> Below are my suggestions:
>
>- Create a clean qt6 supermodule for better maintainability. It's
On Tue, 5 Jan 2021 at 16:55, Volker Hilsheimer
wrote:
>
> Apart from that: is Qt 5.15.2 really so broken that people can’t use it
> without getting more patches?
>
A quick search in Jira gives already 11 "P1: Critical" bugs with Fix
Version 5.15.3.
With 5 issues about crashes, 1 memory leak and
Le lun. 4 janv. 2021 à 15:57, Tuukka Turunen a
écrit :
>
>
> Hi Roland,
>
>
>
> Just so that there is no misunderstanding Qt 5.15.2 release stays
> available for all users, it is just the upcoming LTS phase patch releases
> that will be commercial only. In essence for the open-source users Qt 5.1
Le lun. 4 janv. 2021 à 16:06, Calogero Mauceri a
écrit :
> As far as I understand the next LTS release will be Qt 6.2.
> If 5.15 will not receive any more patches open source users are left
> without LTS till 6.2 is released. Am I correct?
>
> From now on, will LTS releases be available only for
On Mon, 4 Jan 2021 at 14:14, Oswald Buddenhagen
wrote:
> On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote:
> >With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming
> >soon, it is time to enter the commercial-only LTS phase for Qt 5.15
> >LTS.
> >
> that's some brillia
On Wed, 9 Dec 2020 at 10:17, Alexander Nassian <
nass...@bitshift-dynamics.com> wrote:
> 4) Don‘t release a major version that lacks half of the modules of the
> prev version in a hurry for no reason.
>
Especially just after deciding to remove the concept of LTS for open
source users, effectivel
On Tue, 8 Dec 2020 at 17:44, Volker Hilsheimer
wrote:
>
>
> > On 8 Dec 2020, at 16:28, Thiago Macieira
> wrote:
> >
> > On Tuesday, 8 December 2020 01:55:12 PST Giuseppe D'Angelo via
> Development
> > wrote:
> >> Raising the bar: apart from some cases of API problems in 6.0, would it
> >> be fea
On Mon, 21 Sep 2020 at 14:10, Allan Sandfeld Jensen
wrote:
>
> Use the SHA1s in dependencies.yaml
>
>
That's not very practical to do by hand, but it worked.
Thanks
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/li
Hi,
I am trying to contribute to the dev branch of qtwebengine, but I cannot
get it to compile with Qt 5.15.1 or with Qt 6 preview.
With Qt 5.15 the compiler complains that `QWebEngineCertificateError` does
not have a default constructor (required because
of `Q_DECLARE_METATYPE(QWebEngineCertific
On Fri, 28 Feb 2020 at 10:35, Edward Welbourne
wrote:
>
>
> Indeed; most of the case for "emit" can be answered by a sensible naming
> convention.
>
One case where it does not work is in connections.
emit somethingWasDone() and emitSomethingWasDone() look similar.
But the emit in connect(obj,
On Fri, 21 Feb 2020 at 09:24, Kai Köhne wrote:
> Hi,
>
> Another alternative is to actually use C++ attributes for this:
>
> [[qt::emit]] somethingChanged();
>
> C++ attributes are required since C++11, and since C++17 the compiler is
> also required to just ignore one's it doesn't know [1]. Be
On Wed, 29 Jan 2020 at 17:02, Volker Hilsheimer
wrote:
> > On 29 Jan 2020, at 15:20, Benjamin TERRIER wrote:
> > On Wed, 29 Jan 2020 at 14:10, Cristián Maureira-Fredes <
> cristian.maureira-fre...@qt.io> wrote:
> >>
> >> but for Windows/macOS this
On Wed, 29 Jan 2020 at 14:10, Cristián Maureira-Fredes <
cristian.maureira-fre...@qt.io> wrote:
>
> but for Windows/macOS this might have three solutions (maybe more):
> - Using package managers that provide Qt,
> - Download and compile Qt by themselves,
> - Create an account and use the installer
On Tue, 28 Jan 2020 at 17:37, Volker Hilsheimer
wrote:
>
>
> The Qt Company is a public company; we are not yet profitable, but things
> are getting there. Given how significant the Qt Company contribution to Qt
> is, making it a sustainable business should be in the interest of anyone
> that wan
Le mar. 28 janv. 2020 à 03:22, Thiago Macieira
a écrit :
> On segunda-feira, 27 de janeiro de 2020 14:47:46 PST NIkolai Marchenko
> wrote:
> > Assuming we have a VM that is restricted to connecting to the internet,
> we
> > previously could dump the installer there and install Qt.
> > Now, we nee
On Mon, 27 Jan 2020 at 23:23, Ville Voutilainen
wrote:
>
> Correct. Necessary for specific purpose seems to be what article 5
> requires, and then you get explicit consent for that
> specific purpose, and GDPR's articles 5 and 6 are covered (of course
> the rest of article 5's requirements need t
On Mon, 27 Jan 2020 at 23:29, Ville Voutilainen
wrote:
> On Tue, 28 Jan 2020 at 00:17, Cristián Maureira-Fredes
> wrote:
> >
> > Hello David,
> >
> > On 1/27/20 11:00 PM, David Edmundson wrote:
> > >> All security fixes are made available to everyone, for all Qt
> versions that
> > >> they affec
On Mon, 27 Jan 2020 at 22:56, Ville Voutilainen
wrote:
> On Mon, 27 Jan 2020 at 23:43, Benjamin TERRIER
> wrote:
>
> >> I know, but since there's no free right to download binaries, GDPR
> >> doesn't prevent getting explicit consent before allowing
>
On Mon, 27 Jan 2020 at 22:35, Ville Voutilainen
wrote:
> On Mon, 27 Jan 2020 at 23:12, André Somers wrote:
> >
> >
> > On 27/01/2020 22:07, Ville Voutilainen wrote:
> > > On Mon, 27 Jan 2020 at 21:56, Dmitriy Purgin
> wrote:
> > >> By the way, gathering emails by requiring an account to downloa
hrough the installer and the Qt Marketplace to justify the Qt
> Account.“
>
> Yours,
>
> Tuukka
>
> --
> *Lähettäjä:* Development käyttäjän
> Benjamin TERRIER puolesta
> *Lähetetty:* maanantaina, tammikuuta 27, 2020 6:03 ip.
> *Vastaanottaj
My understanding of the agreement between The Qt Company and the KDE Free
Qt Foundation is that if the Qt Company
releases a commercial Qt version without releasing the corresponding
open-source version within 12 months, the ownership of Qt will be
transferred
to the KDE Free Qt Foundation under a
Quoting The Qt Company itslef:
Thanks for your feedback to the new online installer asking for a Qt
> Account signup. We have evaluated the feedback received via the blog,
> various discussion forums, irc and other channels. Based on all these
> comments and discussions with our partners we realiz
Le mar. 5 nov. 2019 à 17:39, Thiago Macieira a
écrit :
>
> Probably *because* events would be processed during the wait. We all know
> nested event loops are bad design. In this case, this stems from another
> bad
> API design: the clipboard handled synchronously, when it clearly isn't.
>
> Note:
2018-02-13 17:22 GMT+01:00 Thiago Macieira :
>
> On terça-feira, 13 de fevereiro de 2018 04:13:20 PST Frederik Gladhorn wrote:
> > Hi all,
> >
> > The Qt Project has been accepted as mentor organization for GSoC. Yay!
> > https://summerofcode.withgoogle.com/organizations/5388456415461376/
>
> That
2018-01-10 11:23 GMT+01:00 Oswald Buddenhagen :
> On Wed, Jan 10, 2018 at 10:37:25AM +0100, Benjamin TERRIER wrote:
> >What happens if the change already exists in the target branch?
> >
> the system would tell you to contact an admin if you tried nonetheless.
2018-01-09 19:09 GMT+01:00 Oswald Buddenhagen :
> On Tue, Jan 09, 2018 at 04:42:51PM +0100, Robert Löhning wrote:
> > Will changes keep their approvals or will those be lost so that
> > approvers have to give them again on the new branch?
> >
> this implementation calls the same underlying script
That's why some software install themselves in user's AppData when the
user does not have admin rights.
Benjamin Terrier
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
2017-04-28 14:23 GMT+02:00 Thiago Macieira :
> On Friday, 28 April 2017 03:56:22 -03 Jani Heikkinen wrote:
>> Yes, MSVC 2017 is already supported in Qt 5.9 and we are trying to get
>> pre-built binaries available before final release; let's see if we can
>> make it happen
>
> I remember a discussi
; and
"QPoint(int(qInf()), int(qInf()))". So in a way it makes sense to check
against "int(qInf())" later in the code, except it is still undefined
behavior.
IMHO a solution could be to change "QPointF::toPoint()" so that for each
coordinate -infinity is casted to std::nume
Hi,
I'd like to get this in before 5.9 FF.
The current state is:
- It works for member functions, function pointers and functors
- It soft breaks existing code that were passing null literals.
- The new functions do not accepts any arguments, users have to use lambda
- The new functions do ac
2017-01-20 3:01 GMT+01:00 Thiago Macieira :
> Because it's a template, so the template when Func = char* matches better than
> the overload with const char*. I assume that using nullptr without casting
> also breaks, correct?
Correct.
> From what you explained, this will not affect the case when
Hi,
I've got an issue.
Adding
template
static typename
QtPrivate::QEnableIf::IsPointerToMemberFunction
&& QtPrivate::FunctionPointer::ArgumentCount == -1
&& !std::is_same::value, bool>::Type
invokeMethod(QObject *object, Func function)
to QMetaObject breaks existing code and the auto tes
2017-01-16 10:34 GMT+01:00 Olivier Goffart :
> On Samstag, 14. Januar 2017 17:28:01 CET Benjamin TERRIER wrote:
> > Hi everyone,
> >
> > I'm trying to contribute by making QMetaObject::invokeMethod() take
> function
> > pointers instead of function names.
>
2017-01-14 18:42 GMT+01:00 Thiago Macieira :
>
> No one can see it while it's a draft. You have to publish the change.
>
>
Ok, it's done.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
e uploaded my change as a draft on gerrit:
https://codereview.qt-project.org/#/c/182339/
Here is the link to the relevant bug report:
https://bugreports.qt.io/browse/QTBUG-37253
I welcome any comment and feedback.
BR,
Benjamin Terrier
___
Development
2016-12-12 10:56 GMT+01:00 Mark De Wit :
> I have an application based on qt-solutions qtwinmigrate sample.
>
> Because we're integrating Qt into an existing MFC application, we're not even
> running QApplication exec. The application uses MFC's entry point for
> startup and drives the Qt event
2016-10-25 16:53 GMT+02:00 Thiago Macieira :
>
> Em terça-feira, 25 de outubro de 2016, às 16:42:43 PDT, Benjamin TERRIER
> escreveu:
> > I just found a bug in 5.8 which make "impossible" to build Qt with MSVC on
> > French systems:
> >
> >
systems as
QT_CL_MAJOR_VERSION and QT_CL_PATCH_VERSION may not be properly set.
Best regards,
Benjamin Terrier
2016-10-24 15:09 GMT+02:00 Jani Heikkinen :
> Hi all,
>
> We have finally (almost) full set of Qt 5.8.0 beta installers for testing
>
>
>
> windows: http://download.qt.io/
Le 10 sept. 2016 12:18 AM, "Edward Welbourne" a écrit :
>
> Benjamin Terrier:
> >> However, my knowledge is that whatever the method one use to generate
> >> your UUID, one can never guarantee its uniqueness. Meaning that the
> >> Qt documentation is fa
e should
be changed.
If anyone can confirm, I'll create a bug report.
BR,
Benjamin Terrier
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
2016-07-11 21:21 GMT+02:00 Sune Vuorela :
> On 2016-07-11, Allan Sandfeld Jensen wrote:
>> On Monday 11 July 2016, Benjamin TERRIER wrote:
>>> QImage::detach() is not public API.
>>> However QPixmap::detach() is, so why QImage::detach() couldn't be made
>>&
2016-07-11 16:03 GMT+02:00 Paul Olav Tvete :
> On mandag 11. juli 2016 12.54.58 CEST Simon Hausmann wrote:
>> Instead of using copy(), why not call the non-const bits() function (and
>> don't use the returned value). That will detach [...]
>
> Instead of using bits(), why not call detach() directly
2016-07-02 16:30 GMT+02:00 Stephen Kelly :
> Benjamin TERRIER wrote:
>
>> But how come a raw loop can be excluding? It should be understandable by
>> any C++ developer and, I would dare to say, by any C-style programming
>> language developer.
>
> I don't th
> However, everyone else is excluded by it. When my colleagues find long
> functions, lots of nested if()s and for()s, ++foo somewhere in while
loops,
> they find it much harder to reason about the code. Now I do too.
>
> So, by sticking to lots of raw loops, you're actually actively excluding
> ot
tps://blog.qt.io/blog/2016/01/13/new-agreement-with-the-kde-free-qt-foundation/
> says that "Qt 5.7 will not be available under LGPLv2.1 anymore" --
> Does that mean LICENSE.LGPLv21 should be removed from the 5.7 branch
> onwards?
>
I'm wondering if having these license f
2015-12-04 10:30 GMT+01:00 Marc Mutz :
> This is precisely the reason why connectSlotsByName is a bad idea in the first
> place; changing the name of a widget breaks connections (at runtime, not at
> compile time as with QObject::connect()).
>
> Just don't use it. Then we can let the function r.i.p
Hi everyone,
This message follows an exchange I've had with Thiago on a bug report:
https://bugreports.qt.io/browse/QTBUG-49749
In the current state, QMetaObject::connectSlotsByName() tries to find,
for each slot named "on__" in a given
object,
a child object named " and connect the signal t
Hi,
For the first point I think it is a good idea.
However the second point seems to be already taken care of. As far as
i know, the current API for obtaining such icons is
QStyle::standardIcon(), looking at its implementation in QCommonStyle,
it calls QPlatformTheme::standardPixmap() for multipl
57 matches
Mail list logo
