On Monday, 22 March 2021 14:55:04 PDT Roland Hughes wrote:
> A deprecation message at compile time is __not__ a warning to the
> installed base. This is especially true for things that were built with
> earlier versions of Qt and are now just being recompiled with a much
> later version.
>
> A mes
On Monday, 22 March 2021 14:29:14 PDT Thorsten Glaser wrote:
> On Mon, 22 Mar 2021, Thiago Macieira wrote:
> > accomplish the same goal. As shown by the example of the KWallet CLI,
> > there
> > may be a much better and much simpler solution once the need is
> > understood.
>
> I wouldn’t call sho
On Wed, 24 Mar 2021 at 04:49, Roland Hughes wrote:
> On 3/23/2021 8:57 AM, Matthew Woehlke wrote:
[...]
> > I'm not actually convinced that paying Qt customers aren't getting the
> > support they paid for; that information is generally not going to be
> > publicly available.
[...]
> The complete i
> I don't know about other parts of the world, but in the U.S.A. the FDA
> is very adamant. Only the binary set that they have tested gets installed.
Pretty much the same in Germany. Also for other safety related (non-medical)
industries.
--
Best Regards,
Bernhard Lindner
___
> Raise your hands.
>
> How many of you have reported bugs that have sat open for over a year?
A year? LOL. 1 year is the age of the newest unresolved issue I have. Most of
them are
many years old, including multiple issues dated 2012.
> Raise your hands.
>
> How many of you have bugs reported
> -Original Message-
> From: Sérgio Martins
> Sent: Dienstag, 23. März 2021 20:40
> To: Maurice Kalinowski
> Cc: Matthew Woehlke ; Volker Hilsheimer
> ; Qt Interest
> Subject: Re: [Interest] The willy-nilly deletion of convenience, methods
>
> On Tue, Mar 23, 2021 at 6:23 PM Maurice K
On Tue, Mar 23, 2021 at 6:23 PM Maurice Kalinowski
wrote:
>
> >
> > Not all deprecations are bad. However, I still maintain that *some* of the
> > Qt
> > 6 changes are problematic. Also, TBH, I think the real issue is less that
> > Qt 6
> > made changes, and more that Qt 5 support got pulled wel
>
> Not all deprecations are bad. However, I still maintain that *some* of the Qt
> 6 changes are problematic. Also, TBH, I think the real issue is less that Qt 6
> made changes, and more that Qt 5 support got pulled well before Qt 6 is
> viable for most folks. That didn't happen with Qt 4 → 5.
>
On 3/23/2021 11:47 AM, Jason H wrote:
QML is a binding environment, and a handy one at that. It is not just GUI.
I have Websocket servers that interact with non-visual classes with bindings
provided in QML. It's great. Yeah the QtQuick controls 1 were terrible and 2
are pretty bad, but I think
Shut up you fucking cunts
Dennis Bean
Director
Dennis B Building Contractors Ltd62 Athol SquareLondonE14 0NPTel: 0207 538
1437Fax: 0207 538 4957
dbeanco...@aol.com
On Tuesday, March 23, 2021, 04:48:10 PM GMT, Jason H wrote:
> Now, the "commercial license" simply could be the Boot2Qt
> Now, the "commercial license" simply could be the Boot2Qt stuff with all
> of Qt being 100% OpenSource. This would provide additional incentive to
> rip QML out so it isn't bastardizing the rest of the product and QML
> could then be its own commercial thing, just for phones. I have lost
> track
On 3/23/2021 10:44 AM, interest-requ...@qt-project.org wrote:
Also, C++ isn't a dictatorship the way Qt is. Anyone can object to any
change, not just on a mailing list, but in person. Anyone can, in theory
(in practice, depending on where you live, there may be a non-trivial
membership fee requi
On 23/03/2021 11.44, Volker Hilsheimer wrote:
I wished I had seen the level of energy y’all are putting right now
into this email thread over the last two years when we discussed
where to go with Qt 6, and when the work actually happened.
IIRC, I complained plenty about QList at the time. I would
On 3/23/2021 8:24 AM, interest-requ...@qt-project.org wrote:
Having read this entire conversation I find it interesting that we as
developers are complaining about features being deprecated and removed in Qt
but yet where is the anger when C++ spec removes features?
https://en.wikipedia.
> On 23 Mar 2021, at 15:49, Matthew Woehlke wrote:
>
> On 23/03/2021 10.36, Benjamen Meyer via Interest wrote:
>> On 3/23/21 10:09 AM, Matthew Woehlke wrote:
>>> Also, C++ isn't a dictatorship the way Qt is. Anyone can object to any
>>> change, not just on a mailing list, but in person. Anyone ca
On 3/23/2021 8:57 AM, Matthew Woehlke wrote:
On 23/03/2021 06.59, Roland Hughes wrote:
30 years is __nothing__ for production systems. It is ordinary for a
well developed system to run 10+ years without any modifications.
On that note, how many people are aware there's a computer that has
bee
Yes good point, take care those built-in size attributes are optional, might
not be there into an SVG, you might not want to count on it.
From: Interest on behalf of Giuseppe D'Angelo
via Interest
Date: Tuesday, March 23, 2021 at 10:53 AM
To: interest@qt-project.org
Subject: Re: [Interest] Q
Il 23/03/21 14:16, Jérôme Godbout ha scritto:
Do you really need to same memory by reducing the source size? I think
you should left the source size alone and sample the image from the full
source. Source size for SVG doesn’t make any sense, it’s vectoriel,
doesn’t have any size, it can scale t
On 23/03/2021 10.36, Benjamen Meyer via Interest wrote:
On 3/23/21 10:09 AM, Matthew Woehlke wrote:
Also, C++ isn't a dictatorship the way Qt is. Anyone can object to any
change, not just on a mailing list, but in person. Anyone can, in theory
(in practice, depending on where you live, there may
On 3/23/21 10:09 AM, Matthew Woehlke wrote:
> On 23/03/2021 09.16, Michael Jackson wrote:
>> Having read this entire conversation I find it interesting that we as
>> developers are complaining about features being deprecated and
>> removed in Qt but yet where is the anger when C++ spec removes
>> f
On 3/23/21 9:25 AM, Matthew Woehlke wrote:
> On 23/03/2021 01.21, Tuukka Turunen wrote:
>> Feedback on the Qt 6 API is valuable and we are very interested in it.
>> Portability was one of the key design principles and we have avoided
>> making changes when not needed. That said, there can surely
>>
On 23/03/2021 09.16, Michael Jackson wrote:
Having read this entire conversation I find it interesting that we as
developers are complaining about features being deprecated and
removed in Qt but yet where is the anger when C++ spec removes
features?
Oh, it's there.
However, C++ is *far* more co
Hello!
QMap::insert(const QMap &) was added in 5.15. No operator+ though.
https://doc.qt.io/qt-5/qmap.html#insert-2
From: Interest on behalf of Jason H
Sent: Tuesday, March 23, 2021 14:52
To: interestqt-project.org
Subject: [Interest] Missing QMap Alge
On 23/03/2021 06.59, Roland Hughes wrote:
30 years is __nothing__ for production systems. It is ordinary for a
well developed system to run 10+ years without any modifications.
On that note, how many people are aware there's a computer that has been
running non-stop for almost 45 years? :-D
I've been in the python world lately and python has a dict.update()
https://python-reference.readthedocs.io/en/latest/docs/dict/update.html
It seems that QMap has no such function anymore, but it also never did? unite()
would make a QMultiMap, so there would be multiple entries rather than one.
On 23/03/2021 01.21, Tuukka Turunen wrote:
Feedback on the Qt 6 API is valuable and we are very interested in
it. Portability was one of the key design principles and we have
avoided making changes when not needed. That said, there can surely
be some items that are unnecessarily changed.
Why
Not sure if it's an option for you guys, but I've been very impressed by the
rapid pace of improvement of Qt/CMake/Git/Linux x-compilation tools in MSVC
over the past couple of years. They have all gone from being semi-supported
add-ons to fully-integrated and functional in the IDE (including ev
On 22/03/2021 23.18, Jason H wrote:
Qt needs to go back to LGPL, or risk getting abandoned/replaced. Seems like
some of the long time users here on this list have come to a similar conclusion.
I've said this before, and I'll say it again: Qt needs to go the way of
OpenOffice.org.
That is, w
Having read this entire conversation I find it interesting that we as
developers are complaining about features being deprecated and removed in Qt
but yet where is the anger when C++ spec removes features?
https://en.wikipedia.org/wiki/C%2B%2B20#Removed_features_and_deprecation
http://www.o
Do you really need to same memory by reducing the source size? I think you
should left the source size alone and sample the image from the full source.
Source size for SVG doesn’t make any sense, it’s vectoriel, doesn’t have any
size, it can scale to any dimension. When playing with the image si
I have never had this experience.
> Sent: Tuesday, March 23, 2021 at 8:12 AM
> From: "Alexander Dyagilev"
> To: interest@qt-project.org
> Subject: Re: [Interest] Qt Creator is so buggy and so slow...
>
> When I press F2 it takes 5 seconds for it to go to symbol definition...
> Constantly using 10
> -Ursprüngliche Nachricht-
> Von: Interest Im Auftrag von Alexander
> Dyagilev
> Gesendet: Dienstag, 23. März 2021 13:13
> An: interest@qt-project.org
> Betreff: Re: [Interest] Qt Creator is so buggy and so slow...
>
> When I press F2 it takes 5 seconds for it to go to symbol definitio
On 3/18/2021 8:38 PM, Alexander Dyagilev wrote:
Hello,
Often it just stops to suggest code, syntax highlighted stops working
(at least for a part of the code) for no apparent reason.
It takes apporx. 10 seconds to parse c++ file for c++ tools to start
working. If you open/close/open same c
When I press F2 it takes 5 seconds for it to go to symbol definition...
Constantly using 100% of CPU. Such a low quality code...
On 3/18/2021 8:38 PM, Alexander Dyagilev wrote:
Hello,
Often it just stops to suggest code, syntax highlighted stops working
(at least for a part of the code) for n
I am assuming that running the application under Valgrind at the client
site to catch the crash is not an option.
Suggestions in order of least amount of pain. Since I see .dll in your
output I will also assume Windows platform.
1.) Run CppCheck and other static source analysis tools to make
On 3/23/21 2:31 AM, interest-requ...@qt-project.org wrote:
On 3/22/2021 7:32 PM, Turtle Creek Software wrote:
Re: willy-nilly
I can relate to anyone who is unhappy about deprecated functions. It is
never fun when existing code breaks. We want to be inventing new stuff,
not going back a
Hello!
Given the issue (heap corruption) and lack of symbols for openssl it's somewhat
hard to determine.
With heap corruption it could be a buffer overflow somewhere else in the
application which is then caught during the malloc call.
Mårten
From: Inte
37 matches
Mail list logo
