On sábado, 21 de janeiro de 2017 17:10:04 PST Olivier Goffart wrote:
> > I mentioned there that Q_NO_TYPESAFE_FLAGS is broken. [...]
> > The define could be removed from qflags.h. Perhaps something could be
> > changed in qnamespace.h to allow the code to compile instead (and make the
> > enum meta
On sábado, 21 de janeiro de 2017 11:30:40 PST Stephen Kelly wrote:
> Hi,
>
> Does anyone know why QFlags has a constructor taking a Zero pointer? My
> guess is that it's a hack to make initializing like
>
> Qt::WindowFlags = 0
>
> work? The problem encountered is that porting tools convert that
On Samstag, 21. Januar 2017 11:30:40 CET Stephen Kelly wrote:
> Hi,
>
> Does anyone know why QFlags has a constructor taking a Zero pointer? My
> guess is that it's a hack to make initializing like
>
> Qt::WindowFlags = 0
>
> work?
Correct.
We want to be able to initialize it with the literal
Hi,
Does anyone know why QFlags has a constructor taking a Zero pointer? My
guess is that it's a hack to make initializing like
Qt::WindowFlags = 0
work? The problem encountered is that porting tools convert that to
Qt::WindowFlags = nullptr
which is undesirable.
https://mail.kde.org/pip
