QLabel returns some CoW types by-pointer as a legacy from Qt 1 times [1]:
QPixmap *QLabel::pixmap() const;
QPixture *QLabel::pixmap() const;
If you know of any other such API, please point them out!
Anyway, a few different ways have been proposed to modernize this API
[2][3][4], summar
> On 16 Aug 2019, at 19:02, Giuseppe D'Angelo via Development
> wrote:
>
> Il 16/08/19 12:26, Lars Knoll ha scritto:
>> As you know, Qt 5.14 will be branched pretty soon. After that I would expect
>> that most new development work would start to be aimed towards Qt 6. As it
>> looks right now,
Il 16/08/19 12:26, Lars Knoll ha scritto:
As you know, Qt 5.14 will be branched pretty soon. After that I would expect
that most new development work would start to be aimed towards Qt 6. As it
looks right now, 5.15 will be a smaller release where we polish what we have in
5.14, and prepare so
On Friday, 16 August 2019 03:26:09 PDT Lars Knoll wrote:
>>> To reflect that and help us all understand that the development
>>> focus is now towards Qt 6, I would like to propose that dev becomes
>>> the Qt 6 branch after we branched away 5.14 (and we merge wip/qt6
>>> back into dev). We can then
16.08.2019, 18:25, "Thiago Macieira" :
> On Friday, 16 August 2019 03:26:09 PDT Lars Knoll wrote:
>> To reflect that and help us all understand that the development focus is now
>> towards Qt 6, I would like to propose that dev becomes the Qt 6 branch
>> after we branched away 5.14 (and we mer
On 16.08.2019 17:23, Thiago Macieira wrote:
> On Friday, 16 August 2019 03:26:09 PDT Lars Knoll wrote:
>> To reflect that and help us all understand that the development focus is now
>> towards Qt 6, I would like to propose that dev becomes the Qt 6 branch
>> after we branched away 5.14 (and we me
On Friday, 16 August 2019 03:26:09 PDT Lars Knoll wrote:
> To reflect that and help us all understand that the development focus is now
> towards Qt 6, I would like to propose that dev becomes the Qt 6 branch
> after we branched away 5.14 (and we merge wip/qt6 back into dev). We can
> then either c
> Sadly, the "Community Edition" is still a binary-only blob.
For what do you need it? Basically it is QtCreator
Just use these designer friendly QtCreator.ini and you have it:
[Core]
CreatorTheme=design
[QML]
Designer\StandAloneMode=true
Designer\EnableTimelineView=true
___
> On 16 Aug 2019, at 12:26, Lars Knoll wrote:
>
> To reflect that and help us all understand that the development focus is now
> towards Qt 6, I would like to propose that dev becomes the Qt 6 branch after
> we branched away 5.14 (and we merge wip/qt6 back into dev). We can then
> either cre
Hi all,
As you know, Qt 5.14 will be branched pretty soon. After that I would expect
that most new development work would start to be aimed towards Qt 6. As it
looks right now, 5.15 will be a smaller release where we polish what we have in
5.14, and prepare some things for Qt 6.
To reflect tha
Hi,
It seems that the presence of QWeakPointer::data() in the past has given
many Qt developers the wrong impression and they're now fighting hard to
keep that impression intact when porting away from deprecated data().
So here's some re-education. Ignore at your own peril :)
= Lesson 1: wea
11 matches
Mail list logo
