Re: [Development] QML instantiation performance

2014-11-28 Thread Gunnar Roth
Hi. on windows that is even worse as  the  qtdeclarative/tests/benchmarks/qml/librarymetrics_performance benchmark is crashing  in many testcases. 5.2.1 runs some more cases than 5.3.2 and 5.4 beta.    the test cases which crash in 5.3.2 and 5.4 beta are: //QTest::newRow("039) listView - with

Re: [Development] changing Q_GADGET

2014-11-28 Thread Julien Blanc
On 28/11/2014 16:13, Gunnar Roth wrote: > Hi Simon > >> 2) On paper it breaks binary compatibility with MSVC, in the unlikely event >> that somebody >> a) produces a DLL and cares about binary compatibility > > Why do you think that is unlikely? > > Actually right now i depend on that. I ge

Re: [Development] changing Q_GADGET

2014-11-28 Thread Gunnar Roth
 Hi Simon   >2) On paper it breaks binary compatibility with MSVC, in the unlikely event >that somebody >a) produces a DLL and cares about binary compatibility   Why do you think that is unlikely? Actually right now i depend on that. I get stuff build against qt 5.2.1 dlls and use that stuff an

Re: [Development] changing Q_GADGET

2014-11-28 Thread Simon Hausmann
On Friday 28. November 2014 12.41.47 Olivier Goffart wrote: > On Friday 28 November 2014 12:19:45 Simon Hausmann wrote: > > Hi, > > > > Monsieur Goffart did awesome work in the dev branch on allowing structures > > with Q_GADGET to have properties and invokable methods. This brings the > > macro t

Re: [Development] changing Q_GADGET

2014-11-28 Thread Simon Hausmann
On Friday 28. November 2014 13.36.56 Al-Khanji Louai wrote: > Out of the box, C++ makes class member declarations private. I quite > strongly feel that changing that behavior in a macro is not what the user > expects. So for me at least the "better API" box is not being checked here > - I quite reg

Re: [Development] changing Q_GADGET

2014-11-28 Thread Al-Khanji Louai
Out of the box, C++ makes class member declarations private. I quite strongly feel that changing that behavior in a macro is not what the user expects. So for me at least the "better API" box is not being checked here - I quite regularly declare private variables under Q_OBJECT and have done so

Re: [Development] changing Q_GADGET

2014-11-28 Thread Milian Wolff
On Friday 28 November 2014 12:41:47 Olivier Goffart wrote: > On Friday 28 November 2014 12:19:45 Simon Hausmann wrote: > > Hi, > > > > Monsieur Goffart did awesome work in the dev branch on allowing structures > > with Q_GADGET to have properties and invokable methods. This brings the > > macro to

Re: [Development] changing Q_GADGET

2014-11-28 Thread Olivier Goffart
On Friday 28 November 2014 12:19:45 Simon Hausmann wrote: > Hi, > > Monsieur Goffart did awesome work in the dev branch on allowing structures > with Q_GADGET to have properties and invokable methods. This brings the > macro to a much wider audience and I'd like to use this opportunity to > propos

Re: [Development] changing Q_GADGET

2014-11-28 Thread Rutledge Shawn
On 28 Nov 2014, at 12:19, Simon Hausmann wrote: > Hi, > > Monsieur Goffart did awesome work in the dev branch on allowing structures > with > Q_GADGET to have properties and invokable methods. This brings the macro to a > much wider audience and I'd like to use this opportunity to propose a

Re: [Development] changing Q_GADGET

2014-11-28 Thread Curtis Mitch
> -Original Message- > From: development-bounces+mitch.curtis=theqtcompany@qt-project.org > [mailto:development-bounces+mitch.curtis=theqtcompany@qt-project.org] > On Behalf Of Simon Hausmann > Sent: Friday, 28 November 2014 12:20 PM > To: development@qt-project.org > Subject: [Deve

[Development] changing Q_GADGET

2014-11-28 Thread Simon Hausmann
Hi, Monsieur Goffart did awesome work in the dev branch on allowing structures with Q_GADGET to have properties and invokable methods. This brings the macro to a much wider audience and I'd like to use this opportunity to propose a slight change to it that may be controversial: The macros Q_OB