Re: [fltk.general] getting parent class

2012-01-17 Thread Edzard Egberts
Greg Ercolano schrieb: > void ShowWidgets_CB(Fl_Widget *w, void*) { > Fl_Window *win = w->window(); // get button's parent window > for ( int i=0; ichildren(); i++ ) { // walk all window's children > const char *classname = "?"; > Fl_Widget *w = win->chil

Re: [fltk.general] fltk 1.1.X to 1.3.0

2012-01-17 Thread Ian MacArthur
On 17 Jan 2012, at 22:16, andy.pa...@baesystems.com wrote: > I have developed an application using v 1.1.X series of fltk over many years, > which places many sub windows at the same place inside the main app, only one > at at time though. > > I have experimented using it with v1.3.0 and it co

[fltk.general] fltk 1.1.X to 1.3.0

2012-01-17 Thread andy . page3
I have developed an application using v 1.1.X series of fltk over many years, which places many sub windows at the same place inside the main app, only one at at time though. I have experimented using it with v1.3.0 and it compiles out of the box, but when it comes to running it the windows now

Re: [fltk.general] getting parent class

2012-01-17 Thread Greg Ercolano
On 01/16/12 23:42, Edzard Egberts wrote: > Greg Ercolano schrieb: >> AFAIK, FLTK doesn't use RTTI; > > But most of the modern compilers use RTTI as default (and even the older > ones can activate it) and so it works, when regarding classes, derived > from FLTK. Neat, thanks Edzard!

Re: [fltk.general] getting parent class

2012-01-17 Thread MacArthur, Ian (SELEX GALILEO, UK)
As Edzard says, you can use RTTI with fltk just fine (though for backward compatibility reasons fltk does not use it itself.) So that may well work out as the best way for you - see Edzard's example. Though I'd only use it (myself) if my code was statically linked, and I'd built my copy of the fl