RE: SUSPECT: Re: [gtkmm] Need a SigC::Signal6 !

[erik_ohrnberger dme net]

Response below....

> -----Original Message-----
> From: Murray Cumming [mailto:murrayc murrayc com]
> Sent: Wednesday, May 19, 2004 9:02 PM
> To: Carl Nygard
> Cc: Ohrnberger, Erik; gtkmm-list gnome org
> Subject: SUSPECT: Re: [gtkmm] Need a SigC::Signal6 !
> 
> 
> On Wed, 2004-05-19 at 08:26 -0400, Carl Nygard wrote:
> > On Wed, 2004-05-19 at 15:35, erik_ohrnberger dme net wrote:
> > > Hi Everyone!
> > > 
> > > 	I'm in need of a SigC::Signal6 in creating my application using
> > > Gtkmm 2.2.8.
> > > 
> > > 	I see that libsigc++-1.2.5 only supports Signal5.
> > 
> > You should be able to implement your own Signal6, it's 
> basic boilerplate
> > code with a touch of induction.
> > 
> > There might be a FAQ or something in the archives, this is 
> not a unique
> > question.
> 
> I think it's far better to make the arguments members of a parent
> object. Functions with a high number of parameters suggest lack of
> object orientation.
>  
> -- 
> Murray Cumming
> murrayc murrayc com
> www.murrayc.com

	In my user interface, I have a list of items that the use can drag
and drop from the this list onto a fixed surface where the dropped object is
then represented by a widget that is created and placed on the fixed widget.


	There are a number of different views of this surface, and these
views are implemented by separate notebooks.  

	So when the primary interface notebook gets a
drag_drop_data_received signal, I need to propagate this signal to the other
notebook views to make the same change occur there.  

	I just seems the most logical to me to connect the
drag_drop_data_recevied signal from each of the alternative view notebooks
to the primary notebook's slot.

	Is it just me, or am I just way off in the weeds here?

	Thanks,
		Erik.