On 27 Aug 2020, at 08:32, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
On 27 Aug 2020, at 08:04, Giuseppe D'Angelo via Development
mailto:development@qt-project.org>> 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
On 27 Aug 2020, at 10:45, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
On 27 Aug 2020, at 08:32, Lars Knoll
mailto:lars.kn...@qt.io>> wrote:
On 27 Aug 2020, at 08:04, Giuseppe D'Angelo via Development
mailto:development@qt-project.org>> wrote:
Hi,
Il 27/08/20 02:46, Thiago Macieira ha
Il 25/08/20 07:49, Thiago Macieira ha scritto:
>> But how about models? This is an honest question. Does it make sense
>> for tables and lists that big? Note that an item*view* has a purpose
>> of being viewed, so how does one display such a huge list, tree or
>> table?
Giuseppe D'Angelo (25
Hi,
Let me start with the good news. bugreports.qt.io is back in business since a
few minutes ago.
We had server issues which prevented Jira from being usable for the first half
of today. Despite our best attempts we were not able fix the corruption.
Therefore we rolled the system back to our
On Thursday, 27 August 2020 00:52:10 PDT Lars Knoll wrote:
> > On 27 Aug 2020, at 09:12, Philippe wrote:
> >>> * QAbstractItemModel
> >>> * QModelIndex
> If I were do design these from scratch, I would certainly use qsizetype
> here, maybe even a qint64 (because one can handle those large data
On Wed, 26 Aug 2020 06:36:27 +
Lars Knoll wrote:
> > * QAbstractItemModel
> > * QModelIndex
>
> I dont think we should port these to use qsizetype.
If you mean, the effort would be too big, or there is lack of resources
to do it, or too many API breaks for Qt 5 to 6, then I can agree.
> On 27 Aug 2020, at 09:12, Philippe wrote:
>
> On Wed, 26 Aug 2020 06:36:27 +
> Lars Knoll wrote:
>
>>> * QAbstractItemModel
>>> * QModelIndex
>>
>> I dont think we should port these to use qsizetype.
>
> If you mean, the effort would be too big, or there is lack of resources
> to do
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 overhead is much worse.
This isn't accurate; QListView (with the default delegate)
> 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
Hi,
Il 27/08/20 16:47, Thiago Macieira ha scritto:
So, can someone take a look at what it would take to make the models use 64-
bit and come up with a proper guide for how to maintain code that compiles and
works on both Qt5 and Qt6? The latter is very important: if you can't easily
maintain
> On 25 Aug 2020, at 18:52, Thiago Macieira wrote:
>
> Can we configure it so the commit message is at least 80 columns wide? Since
> our messages are wrapped at 72 right now but the display is narrower, it's
> causing line-wrapping.
>
As far as I can find, the commit message box
Martin Koller (14 August 2020 17:06) wrote:
> I found myself getting an empty list when using
> QHelpEngineCore::documentsForIdentifier(id) but getting 1 element when
> using the deprecated QHelpEngineCore::linksForIdentifier(id).
Definitely sounds like a bug, although I find no
12 matches
Mail list logo
