Hi,
I would like to provide an update to this (old) thread based on the
development in the past months and weeks.
Am 15.02.19 um 10:30 schrieb Frederik Gladhorn:
> Hi,
>
> On fredag 15. februar 2019 07:31:33 CET Lars Knoll wrote:
>> Summing up the discussion here. It looks like people overall ag
> Well, unfortunetely, even moc doesn't know about all the metatypes.
> Many types don't need registration, and moc is not always aware of the
> Q_DECLARE_METATYPE declaration (but it actually should still work for
> most types)
>
> There are also all the custom QMetaObject (thinking of stuff li
On 16.09.19 12:32, Ulf Hermann wrote:
> [...]
The place where all the metatypes are known at compile time is inside
moc.
Well, unfortunetely, even moc doesn't know about all the metatypes.
Many types don't need registration, and moc is not always aware of the
Q_DECLARE_METATYPE declaration (b
Jani Heikkinen (16 September 2019 12:32)
> It seems this is still badly ongoing. Even Alpha isn't out yet we
> should be able to finalize these as soon as possible. So please do
> reviews now & get reviews approved as soon as possible.
It seems I managed to start the initial review before the fina
On Monday, 16 September 2019 15:21:38 CEST Florian Bruhin wrote:
> I guess with "in 2016" you mean the change this email is talking about:
> https://codereview.qt-project.org/c/qt/qtbase/+/176381
>
> That commit was merged for Qt 5.14 a couple of weeks ago, not in 2016:
Oops! Yes, that's the chan
Hey,
On Mon, Sep 16, 2019 at 07:43:29AM +, Paul Tvete wrote:
> On Friday, 13 September 2019 17:14:32 CEST Thiago Macieira wrote:
>
> > What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
>
> QT_AUTO_SCREEN_SCALE_FACTOR was deprecated in 2016. The recommended
> replacem
> On 13 Sep 2019, at 17:50, Thiago Macieira wrote:
>
> On Friday, 13 September 2019 08:35:59 PDT Elvis Stansvik wrote:
>>> What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
>>
>> I wonder too. I assume they've not been removed? The latter is the one that
>> KDEs kscreen
On 16 Sep 2019, at 13:26, Albert Astals Cid via Development
mailto:development@qt-project.org>> wrote:
El dilluns, 16 de setembre de 2019, a les 13:22:22 CEST, Frederik Gladhorn va
escriure:
On mandag 16. september 2019 12:22:06 CEST Edward Welbourne wrote:
Albert Astals Cid (16 September 2019 1
El dilluns, 16 de setembre de 2019, a les 13:22:22 CEST, Frederik Gladhorn va
escriure:
> On mandag 16. september 2019 12:22:06 CEST Edward Welbourne wrote:
> > Albert Astals Cid (16 September 2019 11:33) wrote:
> > > If i do
> > >
> > > git clone ssh://myu...@codereview.qt-project.org/qt/qtbas
On mandag 16. september 2019 12:22:06 CEST Edward Welbourne wrote:
> Albert Astals Cid (16 September 2019 11:33) wrote:
> > If i do
> >
> > git clone ssh://myu...@codereview.qt-project.org/qt/qtbase
> >
> > I get branch 5.12
> >
> > Given that 5.12 is now on cherry-pick mode (AFAIK) would it m
Hi,
in an effort to enable better tooling for QML, it would be of great
value to have easily accessible per-module descriptions of our meta
types available. This would allow us to analyze the availability of
properties, signals, enums, invokable methods, and slots statically at
compile time. I
Hi all,
It seems this is still badly ongoing. Even Alpha isn't out yet we should be
able to finalize these as soon as possible. So please do reviews now & get
reviews approved as soon as possible.
br,
Jani
From: Development on behalf of Edward
Welbou
Albert Astals Cid (16 September 2019 11:33) wrote:
> If i do
> git clone ssh://myu...@codereview.qt-project.org/qt/qtbase
>
> I get branch 5.12
>
> Given that 5.12 is now on cherry-pick mode (AFAIK) would it make more sense to
> default to branch 5.13?
We have a history of setting a release bran
If i do
git clone ssh://myu...@codereview.qt-project.org/qt/qtbase
I get branch 5.12
Given that 5.12 is now on cherry-pick mode (AFAIK) would it make more sense to
default to branch 5.13?
Cheers,
Albert
P.S: I guess it's the same for the rest of the repos but I have not tried
--
Albert
Den mån 16 sep. 2019 kl 09:44 skrev Paul Tvete :
>
> On Friday, 13 September 2019 17:14:32 CEST Thiago Macieira wrote:
>
> > What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
>
> QT_AUTO_SCREEN_SCALE_FACTOR was deprecated in 2016. The recommended
> replacement is QT_ENABLE_H
On Friday, 13 September 2019 17:14:32 CEST Thiago Macieira wrote:
> What happened to QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS?
QT_AUTO_SCREEN_SCALE_FACTOR was deprecated in 2016. The recommended
replacement is QT_ENABLE_HIGHDPI_SCALING.
It looks like QT_SCREEN_SCALE_FACTORS was
16 matches
Mail list logo
