[Qt-interest] Changing public methods to public slots

[Scott Aron Bloom]

The main reason I can think of is slots (unless you use the KDE based
macros) do not follow privacy schemes.  

Frankly, I would prefer everything be virtual, but that's another
conversation..

Scott

-----Original Message-----
From: qt-interest-bounces at trolltech.com
[mailto:qt-interest-bounces at trolltech.com] On Behalf Of
variadic.template
Sent: Saturday, December 26, 2009 4:50 PM
To: qt-interest at trolltech.com
Subject: [Qt-interest] Changing public methods to public slots

Hi,

I'm currently writing an application with QGraphicsView and all these  
things, no problem
there, in general. I have the need of calling some methods of  
QGraphicsView through slots,
like centerOn(...). So I'm going to derive from QGraphicsView and wrap
the  
methods
I need and writing some slots for them - and that time the question
"Why?"  
hits in my face.
I think that's something common and, at the same time, very annoying.  
What's the reason
for not-declaring all/most of the methods as slots? Of course, there
will  
be more things to do
for the compiler (generating *_moc and compiling it), the libraries will

become bigger -
but the developing itself could become more efficient. Did somebody  
already try how big
the libraries would be if all (public-) methods would be slots? Are
there  
any other
reasons why this approach would be a bad idea?

Hendrik

_______________________________________________
Qt-interest mailing list
Qt-interest at trolltech.com
http://lists.trolltech.com/mailman/listinfo/qt-interest