> * Support for generating debug info in PDB format
How useful is this? Does gdb support this format? If not, then you wouldn't be
able to debug stuff, meaning this is not a benefit at all.
===
I haven't tried this, however, according to what I have read this enables you
to build
My two bits as a user of Qt. Please make sure any exposed headers use the
old-school guards and NOT the #pragma once.
I don’t care how the internal Qt headers work. However, Ive been burned too
many times by the "known issues" of the #pragma once to want to use them.
The problem isn’t if the
I was able to work out the issues, but I have two recommendations for QNAM
1. If you don't have openssl properly installed, and you attempt to make a
https connection, it should give an ssl error
* While Ive dealt with this issue a number of times, it continually
bites me in the butt
On Behalf Of Thiago
Macieira
Sent: Wednesday, July 27, 2022 2:50 PM
To: development@qt-project.org
Subject: Re: [Development] [Announce] Security advisory: Freetype in Qt
On Wednesday, 27 July 2022 14:28:05 PDT Scott Bloom wrote:
> Outside opinion. I know many non-commercial who tend to st
Outside opinion. I know many non-commercial who tend to stick with the LTS for
their projects.
Scott
-Original Message-
From: Development On Behalf Of Thiago
Macieira
Sent: Wednesday, July 27, 2022 1:23 PM
To: development@qt-project.org
Subject: Re: [Development] [Announce] Security
Adding a +1 here.
Where I have created a “similar” treeview with tableview similarities is when
viewing SQL data results.
The tree aspect, represents the sorted on column with duplicate data. For
instance, say you had a model that was
Firstaname, lastname, address, city, state, zipcode and
On linux, you can overwrite most of the QStandardPaths using the XDG_
environment variables.
However, I don't see anyway to do the same for Windows. Windows appears always
goes to the systems SHGetKnownFolderPath.
In a similar manner to QSettings being able to set a specific directory, I
Why wouldn’t they simply have two versions of Qt ( or more) the one they are
targeting for desktop, and the previous one they are targeting for
android/"remote"
-Original Message-
From: Development On Behalf Of Joerg
Bornemann
Sent: Friday, November 5, 2021 2:28 AM
To: Volker
The sad part in all this.. the amount of negative discussion about Qt, when
TQtC could fix this easily, simply maintain LTS at the opensource license.
If they want patch releases in general not to be open source fixes, fine. Ie
6.1 is opensource, 6.1.1 is not.. But when a LTS is released,
One thing to consider here.
Visual Studio is now shipping CMake, its also getting updated for patches of a
given version of VS, and is not the same from VS 2019 or VS 2017
I know of a couple of teams that are using the VS version of CMake on windows
to alleviate the need for another
On Monday, 4 January 2021 20:32:27 -03 Scott Bloom wrote:
> The funny thing, I remember at a Qt Dev Days when Qt 5 was about a
> year away. The "we will never do a Qt 3-4 type major version change
> again" was said time and time again.
>
> Where functionality was miss
-Original Message-
From: Development On Behalf Of Kevin
Kofler via Development
Sent: Monday, January 4, 2021 3:16 PM
To: development@qt-project.org
Subject: Re: [Development] Spam: Re: Commercial-only LTS phase starts: Closing
the 5.15 branch(es) on 5th January
Oswald Buddenhagen
So I wanted bring up some issues the company I work for is having using 5.12
and 5.15.
Our customers (IC development companies large and small) are extremely slow to
move their OS. We had customers who are still using CentOS 6.X . These
customers, often will NOT move OS’s once a project has
> On 27 Aug 2020, at 08:04, Giuseppe D'Angelo via Development
> wrote:
>
> Hi,
>
> Il 27/08/20 02:46, Thiago Macieira ha scritto:
>> A QListView of 2 billion lines with where each line is a QString one
>> to 7 characters in length would be 2G * (24 + 32) = 96 GB of memory use.
>> QListWidget's
From: Development On Behalf Of Ville
Voutilainen
Sent: Wednesday, August 26, 2020 12:08 AM
To: Lars Knoll
Cc: Qt development mailing list
Subject: Re: [Development] qsizetype and classes working with QStrings or QList
On Wed, 26 Aug 2020 at 09:39, Lars Knoll wrote:
> > QtGui:
> > *
Or
for( auto ii = 0; ii < std::vector.size(); ++ii )
{
}
since there is no suffix for "size_t" and the size of size_t will depend on 64
vs 32 bits whats the best way to AAA the index iterator?
Scott
-Original Message-
From: Development [mailto:development-boun...@qt-project.org] On
Thanks!
-Original Message-
From: Kevin Funk
Sent: Monday, March 9, 2020 2:56 PM
To: development@qt-project.org
Cc: Scott Bloom ; Development@qt-project.org
Subject: Re: [Development] What project are Qt+CMake bugs part of
On Monday, 9 March 2020 22:15:02 CET Scott Bloom wrote:
>
I found a bug in Qt5CoreMacros.cmake where on windows in a path with the
QT5_MAKE_OUTPUT_FILE macro constructs invalid file names.
What project should this be filed against in JIRA?
Scott
___
Development mailing list
Development@qt-project.org
From: Development [mailto:development-boun...@qt-project.org] On Behalf Of
André Pönitz
Sent: Monday, February 3, 2020 3:50 PM
To: Giuseppe D'Angelo
Cc: development@qt-project.org
Subject: Re: [Development] The future of smart pointers in Qt API
On Mon, Feb 03, 2020 at 10:25:40PM +0100,
Re-reading Mark's initial post. One thing, that I had requested from the
trolls almost 20 years ago.. which Ill put out there again, is a
"non-developer" license that allows people who don’t develop using Qt, but the
product they work on uses it somewhere, and thus its required to build.
For
From: Development [mailto:development-boun...@qt-project.org] On Behalf Of
Elvis Stansvik
Sent: Saturday, January 18, 2020 4:33 AM
To: Sze Howe Koh
Cc: Qt development mailing list
Subject: Re: [Development] Rationalizing qApp and qGuiApp
Den lör 18 jan. 2020 kl 11:05 skrev Sze Howe Koh :
>
>
On Saturday, 15 June 2019 12:22:34 PDT Bogdan Vatra via Development wrote:
> > Why must they be built in one go? Why can't they be separate builds
> > stitched together? Or even completely separate builds as on Linux
> > and all the other Unix?
>
> Because qmake can build them in one go and
I'm a bit late to this game, but ...
> I don’t see why you’d want to remove the switch for Qt 6.
> It would be a porting help for application developers.
Application developers will not build their own Qt, but rely on the QList with
the switch their Qt and Qt-using 3rd party libraries are
breaking half of the world (i.e. no final decision so far) and this
discussion started long time ago, so you've had (and still have plenty of) time
to revisit usages of QList in your codebase and replace it with more
appropriate container.
> 17 мая 2019 г., в 19:47, Scott Bloom написа
On Friday, 17 May 2019 09:38:05 PDT Marco Bubke wrote:
> Thiago, you partially implying that BC is still needed but with
> technologies like flatpak or snappy this will maybe not common use
> case anymore. They provide even behaviour compatibility if you stay with the
> same runtime.
>
On Friday, 3 May 2019 10:22:20 PDT Daniel Teske wrote:
> std::unique_ptr rightButton =
> std::make_unique("RIGHT");
> layout->addWidget(std::move(rightButton));
The problem in this particular example is that once you've added the widget,
the rightButton smart pointer no longer has a pointer.
-Original Message-
From: Development On
Behalf Of Thiago Macieira
Sent: Tuesday, July 31, 2018 11:41
To: development@qt-project.org
Subject: Re: [Development] Qt 6 buildsystem support requirements
On Tuesday, 31 July 2018 11:15:50 PDT Ville Voutilainen wrote:
> This provoked a
> I cant even get my developers to agree the emacs takes to many fingers, and
> VI(m) is the only editor they need
>
> Let alone, where the brackets and spaces belong
>
> Let alone, if statements on the same line as the conditional
>
> The problem ive seen, is while you may LOVE the
o take care of code-formatting, thanks to clang-format, eases
programming.
And looking at someone else code with a familiar format, gives the feeling "I
am home" (provided some naming guideline is respected).
Philippe
On Fri, 22 Jun 2018 15:34:09 +
Scott Bloom wrote:
> Fair enough
29 matches
Mail list logo
