[Qt-interest] Changing public methods to public slots
Scott Aron Bloom
Scott.Bloom at sabgroup.com
Mon Dec 28 17:53:29 CET 2009
Im not a KDE guy... But I was under the impression, that KDE had a method of protecting private/protectred slots from being called from no derived classes (or non-self)
I just remember reading it somewhere, in a previous thread talking about this same topic
Scott
-----Original Message-----
From: qt-interest-bounces at trolltech.com [mailto:qt-interest-bounces at trolltech.com] On Behalf Of Thiago Macieira
Sent: Monday, December 28, 2009 4:54 AM
To: qt-interest at trolltech.com
Subject: Re: [Qt-interest] Changing public methods to public slots
Em Segunda-feira 28. Dezembro 2009, às 11.36.23, Stephen Kelly escreveu:
> Scott Aron Bloom wrote:
> > The main reason I can think of is slots (unless you use the KDE
> > based
> > macros) do not follow privacy schemes.
>
> What macros are these?
There aren't any.
But Scott may be thinking of Q_PRIVATE_SLOT, which doesn't change the privacy scheme either.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
More information about the Qt-interest-old
mailing list