Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

On Monday 07 March 2016 20:55:11 Curtis Mitch wrote: > Recently I noticed this sentence in QObject's documentation [1]: > > We strongly recommend the use of this macro in all subclasses of QObject > regardless of whether or not they actually use signals, slots and > properties, since failure to do

Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

On Mon, Mar 07, 2016 at 08:21:54PM +, Curtis Mitch wrote: > Thanks guys. > > Is this worth mentioning in the documentation? I think it would make sense to list the features that are affected so that users can decide whether they actually need one of them, or not, instead of having this unspec

Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

Op 07/03/2016 om 21:21 schreef Curtis Mitch: Thanks guys. Is this worth mentioning in the documentation? It already says so, right? I don't think it is needed to specify exactly what breaks. André From: Development on behalf of Giuseppe D'Angelo

Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

On Mon, Mar 07, 2016 at 07:55:11PM +, Curtis Mitch wrote: > Recently I noticed this sentence in QObject's documentation [1]: > > We strongly recommend the use of this macro in all subclasses of QObject > regardless of whether or > not they actually use signals, slots and properties, since fai

Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

Thanks guys. Is this worth mentioning in the documentation? From: Development on behalf of Giuseppe D'Angelo Sent: Monday, 7 March 2016 21:19 To: development@qt-project.org Subject: Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that

Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

Il 07/03/2016 20:55, Curtis Mitch ha scritto: Why is this the case? What strange behaviour could result from not doing so? qobject_cast breaks; the meta object system reports and uses the wrong class name (so things like "inherits", "className" etc. don't work); tr() uses the wrong context; a

Re: [Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

Op 07/03/2016 om 20:55 schreef Curtis Mitch: Recently I noticed this sentence in QObject's documentation [1]: We strongly recommend the use of this macro in all subclasses of QObject regardless of whether or not they actually use signals, slots and properties, since failure to do so may lead

[Development] Usage of Q_OBJECT macro in QObject subclasses that don't use signals, slots, or properties

Recently I noticed this sentence in QObject's documentation [1]: We strongly recommend the use of this macro in all subclasses of QObject regardless of whether or not they actually use signals, slots and properties, since failure to do so may lead certain functions to exhibit strange behavior.

Re: [Development] QtQuick Call for Maintainer

I'm sorry to see you step down, Alan. Thanks for all the good work! I would like to suggest Robin Burchell for the role of future Qt Quick maintainer. He is a long time Qt contributor and has repeatedly shown insight and dedication to the project. From various work he has solid experience build

Re: [Development] QtQuick Call for Maintainer

On 08/03/16 01:13, Frederik Gladhorn wrote: I'd like to propose Shawn Rutledge as maintainer for Qt Quick. +1 -- Software Engineer Hardware Enablement Canonical Ltd ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/

Re: [Development] QtQuick Call for Maintainer

Hello Alan, thanks a lot for all the work you've done! On Saturday, March 05, 2016 11:40:56 PM Alan Alpert wrote: > Hi all, > > I have been drawn away from Qt Quick at work the past several months, > for even I do not write back-end services with Qt Quick. Consequently > I have not had time to f

Re: [Development] codereview.qt-project.org certificate has expired

Hi, Yes, this is in progress. Unfortunately the renewal email went to a wrong address. We'll hopefully get new certificate in place very soon. Yours, Tuukka > -Original Message- > From: Development [mailto:development- > bounces+tuukka.turunen=theqtcompany@qt-project.org]