If you're only getting the problem when building your own code, but not when building FLTK itself, check your code for casing typos for the #include files. a common mistake is #include <Fl/Fl_Bla_Bla.H> instead of #include <FL/Fl_Bla_Bla.H> (note case on first 'L')
Such a problem could cause your #include's to come from a previously 'installed' FLTK (eg. /usr/include/) instead of the lib your building against, eg. /usr/local/src/fltk-x-x-x/. Marc R.J. Brevoort wrote: > On Sat, 9 Oct 2010, Ian MacArthur wrote: > >> It is *possible* that your tabs problem is related though, I have in the >> past accidentally created Frankenstein builds that were part 1.1 and >> part 1.3 and the code sometimes would actually run, but then do very odd >> things... >> >> I guess a complete clean and rebuild wouldn't hurt, just in case. > > Well, I guess I'll have to search on. After doing this, I'm still > getting the same behaviour. It's only on that particular tab, too. > > What happens is that that particular tab is showing fragments of > other tabs which it seems to be redrawing even though they're not > visible. The strange bit is, only tabs previously visited will > blend into the tab exhibiting this *weird* behaviour. > > I can't imagine what could be causing it. I guess I'll try a > full clean and a rebuild with 1.1.7 to see if that does > anything (I *know* I've at least seen things work fine with > 1.1.7 so maybe that will help me rule out some kind of > regression). > > Best, > Marc > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
