> >> 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.
Yes - though it looks like in some cases it is triggering a "regression" in so far as code that worked with 1.1 no longer links correctly... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
