[Kde-games-devel] Re: About kbackgammon
Andreas Beckermann
b_mann at gmx.de
Tue Sep 23 01:37:46 CEST 2003
On Tuesday 23 September 2003 00:21, Albert Astals Cid wrote:
> A Dimarts 23 Setembre 2003 00:07, Andreas Beckermann va escriure:
> > On Monday 22 September 2003 23:45, Albert Astals Cid wrote:
> > [...]
> >
> > > Then a thing about KGame. In kbackgammon/engines/nextgen/kbgng.cpp
> > > there are connect that refer to KGame signals (like signalPlayerInput)
> > > that seem that sometimes existed but they do not exist now.
> > >
> > > Also i find strange that
> > >
> > > grep signalPlayerInput *
> > > COMPAT:18.09.2001: Question: Should the signal
> > > signalPlayerInput(QDataStream &,KPlayer *))
> >
> > The rest of this paragraph describes how to replace signalPlayerInput().
> > If you take a closer look at KBackGammon code, you'll see that exactly
> > this was done there. You can remove the entire slotPlayerInput() in HEAD
> > kbackgammon, it is never called anyway.
>
> Uh, that happens because of grepping :-/
>
> But i think the code about slotPlayerInput() in HEAD is really called
> because opening kbackgammon and going to settigns -> configure outputs
>
> QObject::connect: No such signal
> KBgGame::signalPlayerInput(QDataStream&,KPlayer*)
> QObject::connect: (sender name: 'unnamed')
> QObject::connect: (receiver name: 'kbackgammon')
>
> to the shell so it means the code is beign called, isn't it?
This means the connect() is called, but the slot will not be called (as there
is no such signal).
> > Feel free to fix all outstanding bugs in docs and code ;-)
>
> Too much work right now, i'll try when i get a bit of free time.
Next weekend, ok?
CU
Andi
More information about the kde-games-devel
mailing list