🚀 go-pugleaf

In article <CHAN.91Jun23132258@icsid2.comp>, chan@icsid2.comp (Pamela Chan) writes:
|> I'm trying to associate a callback funtion with a simple 
|> push button. I was looking at the sample program <alert.c> 
|> in the standard distribution. It works fine if I assigned 
|> World::quit as the callback function, but anything else will 
|> generate a compiler error:
|> 
|> Glyph* MakeControlPanelDialog(Font* f, Color* fg, TestButton* tbutton) {
|> 
|>    Button* button1 = new Button(
|> 
|> //   *******error occurs here**********
|>      new ActionCallback(TestButton) (&tbutton, TestButton::Press),
|> 
|> //   replace the above line with the following and it works fine
|> //   new ActionCallback(World) (&world, &World::quit),
|> 
|> "main.c", line 31: error: bad argument list for 
|> TestButton_ActionCallback::TestButton_ActionCallback() 
|> (no match against any  TestButton_ActionCallback::TestButton_ActionCallback())
|> 1 error

The problem is you pass ``&tbutton'' instead of ``tbutton''.  The constructor wants
a pointer to a TestButton (or more generally the callback receiver type).  The alert program
uses ``&world'' because world is declared as an object instead of a pointer.