On 13.05.2011, at 10:39, Eduardo Suarez wrote: >> Is that the same circumstance that you are seeing, i.e. fluid-1.3 = >> processing a fluid-1.1 input file? >> > It seems the case. > >> If so, it may be the case that simply editing the file a bit in = >> fluid-1.3 then re-saving it would trigger a different parsing of the = >> file? I'm totally guessing now, of course... >> > I opened the 'fl' file in fluid, create empty code nodes for the undefined > methods, and saved it. That solved the problem.
Ah, yes, I remember. That was an optimization that we did: empty definitions doe not get written as functions anymore. It seemed useful at that time. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
