paragui-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [paragui-users] Signals and Slots


From: Alexander Pipelka
Subject: Re: [paragui-users] Signals and Slots
Date: Mon, 18 Jul 2005 10:10:16 +0200

Yes. Oops. Sorry, didn't see your reply. :)

Am Sonntag, den 17.07.2005, 13:13 +0200 schrieb Ulf Lorenz:
> On Sun, Jul 17, 2005 at 12:02:56PM +0300, Dimitris Mexis wrote:
> > clsStartUp::clsStartUp( struct GfxOptions & gfxOptions, PG_Widget * 
> > parent, PG_Rect r, char * windowtext ):
> > pgWindow( parent, r, windowtext) <---------Just the constructor, just to 
> > show you where it lies
> > 
> > this is my line that emits a signal...
> > {
> > rdoNation->sigClick.connect( slot( *this, &clsStartUp::handle_selectitem 
> > ) );
> >    PG_RadioButton & rdm = rdoNation[0];
> > }
> > 
> > This is the slot...
> > bool clsStartUp::handle_selectitem( PG_Pointer clientdata )
>                                       ^^^^^^^^^^^^^^^^^^^^^
> 
> Maybe you are missing an asterisk here. 'PG_Pointer' is defined as 'void'.
> However, what you want is a 'void*'.
> Does rewriting this to "PG_Pointer* clientdata" help?
> 
> 
> By the way, paragui signals also allow you to take the PG_RadioButton
> directly. I.e. a PG_RadioButton::sigClick automatically supplies the
> instance that triggered it, so that the line
> 
> bool clsStartUp::handle_selectitem( PG_RadioButton* btn )
> 
> should also work; this saves a useless cast.
> 
> 
> Ulf
> 
-- 
Alexander Pipelka

BMS Bayer GmbH
Thimiggasse 35/12
A-1180 Wien

Phone:  +43 1 524 81 3400
Fax:    +43 1 524 81 3480
Web:    www.bms-austria.com






reply via email to

[Prev in Thread] Current Thread [Next in Thread]