On 17.01.2012 10:32, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I guess what I'd really want is a macro like:
I_AM_LINKING_STATIC_SO_GIVE_ME_THE_LATEST_AND_GREATEST_ABI_OPTIONS
(well, maybe the actual name might be shorter than that) to get at the
latest supported ABI without having to
On 01/17/12 01:32, MacArthur, Ian (SELEX GALILEO, UK) wrote:
I guess what I'd really want is a macro like:
I_AM_LINKING_STATIC_SO_GIVE_ME_THE_LATEST_AND_GREATEST_ABI_OPTIONS
(well, maybe the actual name might be shorter than that) to get at the
latest supported ABI without having to
HI,
Please FLTK developer try to find a way to collect the small projects (small
extra library that is an extentions for fltk).
As you didn't like my suggestion for the git , and it is up to you to do so
but collecting the widgets beside the core FLTK is very important. Many
questions in
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
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!
Greg Ercolano schrieb:
void ShowWidgets_CB(Fl_Widget *w, void*) {
Fl_Window *win = w-window(); // get button's parent window
for ( int i=0; iwin-children(); i++ ) { // walk all window's children
const char *classname = ?;
Fl_Widget *w =
6 matches
Mail list logo
