Re: [ROOT] Problems with TGPopupMenu::Associate()

From: Fons Rademakers (Fons.Rademakers@cern.ch)
Date: Sat Feb 09 2002 - 15:55:27 MET


Hi Brett,

  yes Associate() is only needed to tell the popup menu which widget
will process its messages (or better use Connect() to bind the menu
signals to some slot method).

I did not point this out when initially replying to you since I was
totally overloaded at the end of Friday evening. ;-)

Cheers, Fons.



On Fri, 2002-02-08 at 22:54, Brett Viren wrote:
> Fons,
> 
> I think I misunderstood Associate() completely.  The fMsgWindow data
> member is not needed to handle the physical popping up of menus (which
> I what I thought), but rather to notify observers that the menu popped
> up, right?
> 
> Since I am observing menu actions via overriding the the Activated()
> method, how and when Associate() is called doesn't effect me, so I'll
> just leave it alone.
> 
> Sorry for the noise.
> 
> -Brett.
-- 
Org:    CERN, European Laboratory for Particle Physics.
Mail:   1211 Geneve 23, Switzerland
E-Mail: Fons.Rademakers@cern.ch              Phone: +41 22 7679248
WWW:    http://root.cern.ch/~rdm/            Fax:   +41 22 7679480



This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:41 MET