[fltk.general] Fl_OpDesk again

2012-01-16 Thread Bernhard Schönhammer
Hi again, just another small question: void Fl_OpBox::_RemoveButton(Fl_OpButton *but) removes the but from inputs and outputs. Shouldn't it remove it from the Fl_Group too? Regards, Bernhard ___ fltk mailing list fltk@easysw.com

Re: [fltk.general] Fl_OpDesk again

2012-01-16 Thread Greg Ercolano
On 01/16/12 08:26, Bernhard Schönhammer wrote: Hi again, just another small question: void Fl_OpBox::_RemoveButton(Fl_OpButton *but) removes the but from inputs and outputs. Shouldn't it remove it from the Fl_Group too? Yes, I'd agree. I don't think the test

[fltk.general] getting parent class

2012-01-16 Thread ORL
Hi! I'm new here, and I'm not quite a developper. I'm a musician, and use fltk/fluid to design small and simple OSC interfaces. I need to get the parent of a Fl_Box type to determine what the handle method does. To be more accurate, I need to check if the parent class is light_xyPad (which is

Re: [fltk.general] getting parent class

2012-01-16 Thread Greg Ercolano
On 01/16/12 14:28, ORL wrote: I need to get the parent of a Fl_Box type to determine what the handle method does. To be more accurate, I need to check if the parent class is light_xyPad (which is a class I've written, quite close to Fl_Group, but with some private variables).

Re: [fltk.general] getting parent class

2012-01-16 Thread Edzard Egberts
Greg Ercolano schrieb: On 01/16/12 14:28, ORL wrote: I need to get the parent of a Fl_Box type to determine what the handle method does. To be more accurate, I need to check if the parent class is light_xyPad (which is a class I've written, quite close to Fl_Group, but with some private