Moveing KDevelop from python

Bernd Gehrmann Bernd-Gehrmann at gmx.de
Mon May 6 21:29:02 UTC 2002


On Monday 06 May 2002 20:40, you wrote:
> On Monday 06 May 2002 7:34 pm, Richard Dale wrote:
> ...
>
> > connect( myScriptingProxy, SIGNAL(signalKDevelop(int)),
> >              aKDevelopInstance, SLOT(doKDevelopAction(int)) );
>
> Correction, it would have to be something like:
>
> char * myTargetSlot = "1doKDevelopAction(int)";
> connect( myScriptingProxy, SIGNAL(signalKDevelop(int)),
>              aKDevelopInstance, myTargetSlot   );
>
> So that myTargetSlot can vary at runtime.

Interesting, I wouldn't have thought of that way. There is a
limitation in this approach though: signal/slot connections
can't have return values.

Bernd.




More information about the KDevelop-devel mailing list