[Kde-bindings] Qyoto: SIGNALS/SLOTS

[Richard Dale]

On Friday 23 December 2005 22:33, Arno Rehn wrote:
> > Ahh, that is cool.  I had something similar for libqtsharp.  So, Arno, it
> > looks like the problem you were having was you were trying to connect the
> > smoke object directly, instead of the underlying QObject which is the
> > void ptr.  However, I think Richard is absolutely right, you don't want
> > to be using Qt#'s libqtsharp for signal/slot connections on the C/C++
> > side of things when SMOKE will provide this for you.  Better to do it the
> > SMOKE way since that is the binding library.
>
> Ok, I think I can do it now the 'non-SMOKE-way'. But I agree it would be
> better to do it the SMOKE way. But what would that be?
That involves building QMetaObjects on the fly, and overriding qt_emit() and 
qt_invoke() instead of having a 'proxy slot' class with all the possible 
slot/arg types in the Qt toolkit. In qtruby the QMetaObjects are constructed 
by both ruby and C++ code (see make_metaObject() in Qt.cpp and related 
functions), so it might be possible to do it the same way in Qyoto.

-- Richard