On joi, 28 iulie 2016 09:52:56 EEST Dominik Holland wrote:
> Am 28.07.16 um 09:41 schrieb Olivier Goffart:
> > On Donnerstag, 28. Juli 2016 10:32:54 CEST BogDan Vatra wrote:
> >> On miercuri, 27 iulie 2016 09:08:32 EEST Thiago Macieira wrote:
> >>> On quarta-feira, 27 de julho de 2016 11:47:03 PDT
Am 28.07.16 um 09:41 schrieb Olivier Goffart:
> On Donnerstag, 28. Juli 2016 10:32:54 CEST BogDan Vatra wrote:
>> On miercuri, 27 iulie 2016 09:08:32 EEST Thiago Macieira wrote:
>>> On quarta-feira, 27 de julho de 2016 11:47:03 PDT BogDan Vatra wrote:
On miercuri, 27 iulie 2016 10:35:01
On Donnerstag, 28. Juli 2016 10:32:54 CEST BogDan Vatra wrote:
> On miercuri, 27 iulie 2016 09:08:32 EEST Thiago Macieira wrote:
> > On quarta-feira, 27 de julho de 2016 11:47:03 PDT BogDan Vatra wrote:
> > > On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote:
> > > > Op 27/07/2016 om
On miercuri, 27 iulie 2016 09:08:32 EEST Thiago Macieira wrote:
> On quarta-feira, 27 de julho de 2016 11:47:03 PDT BogDan Vatra wrote:
> > On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote:
> > > Op 27/07/2016 om 09:53 schreef BogDan Vatra:
> > > Would that not break existing QML
On quarta-feira, 27 de julho de 2016 11:47:03 PDT BogDan Vatra wrote:
> On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote:
> > Op 27/07/2016 om 09:53 schreef BogDan Vatra:
> > Would that not break existing QML applications that now use enums backed
> > by scoped enums in C++?
>
> It
On Wed, Jul 27, 2016 at 10:47 AM, BogDan Vatra wrote:
> Of course if we can find a better solution to have them both is even better !
I guess you'll need a pragma to enable this feature as opt-in. And/or
a pragma to warn about the other usage so that in 5.10/5.11 you can
break
On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote:
> Op 27/07/2016 om 09:53 schreef BogDan Vatra:
> >> That said, it would be a behavior change not to allow anymore the
> >> previous
> >> (unscoped) syntax to work with QML
> >
> > The unscoped enums should work as they are woring now,
Op 27/07/2016 om 09:53 schreef BogDan Vatra:
That said, it would be a behavior change not to allow anymore the previous
(unscoped) syntax to work with QML
The unscoped enums should work as they are woring now, just the scoped ones
should be scoped in QML as well.
Based on your patch, I'll
On marți, 26 iulie 2016 20:08:52 EEST Olivier Goffart wrote:
> On Dienstag, 26. Juli 2016 08:33:31 CEST Thiago Macieira wrote:
> > Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra
escreveu:
> > > Hi,
> > >
> > > Is there any reason why C++11 scoped enums are not scoped in QML ?
Em terça-feira, 26 de julho de 2016, às 20:08:30 PDT, BogDan Vatra escreveu:
> scoped enums are declared differenty : enum *class* MyEnum :)
> Even more, scoped enums in C++ must me used with fully qualified name
> *MyEnum a = MyEnum.Val1* not *MyEnum a = Val1*, so a scoped enum is not
> exacly
On Dienstag, 26. Juli 2016 08:33:31 CEST Thiago Macieira wrote:
> Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu:
> > Hi,
> >
> > Is there any reason why C++11 scoped enums are not scoped in QML ?
>
> There's no trait to tell apart a scoped enum from an unscoped one.
On marți, 26 iulie 2016 08:33:31 EEST Thiago Macieira wrote:
> Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu:
> > Hi,
> >
> > Is there any reason why C++11 scoped enums are not scoped in QML ?
>
> There's no trait to tell apart a scoped enum from an unscoped one. An
Em terça-feira, 26 de julho de 2016, às 17:41:01 PDT, Giuseppe D'Angelo
escreveu:
> On Tue, Jul 26, 2016 at 5:33 PM, Thiago Macieira
>
> wrote:
> > This is all the engine sees. It's an enum.
>
> But moc might help in this, extracting the relevant information
>
On Tue, Jul 26, 2016 at 5:33 PM, Thiago Macieira
wrote:
> This is all the engine sees. It's an enum.
But moc might help in this, extracting the relevant information
alongside the enum's metadata.
Also if std::is_enum::value is true and std::is_convertible
Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu:
> Hi,
>
> Is there any reason why C++11 scoped enums are not scoped in QML ?
There's no trait to tell apart a scoped enum from an unscoped one. An enum is
en enum, that's all.
If you want a given enum to be scoped in
Hi,
Thanks for the super quick reply !
I created a bug report for you here https://bugreports.qt.io/browse/
QTBUG-54961 .
Cheers,
BogDan.
On marți, 26 iulie 2016 14:54:46 EEST Simon Hausmann wrote:
> Hi,
>
>
> By the time this aspect of the QML engine was implemented, C++11 scoped
> enums
Hi,
By the time this aspect of the QML engine was implemented, C++11 scoped enums
did not exist. I think it would be fine
to add this feature to the JavaScript bindings for C++ classes.
Simon
From: Development
17 matches
Mail list logo