> In fact I'm not using fluid. You must be using fluid: you are presenting fragments of fluid output here, which you presumably must be translating into C++ for compilation, and AFAIK fluid is the only tool around that knows how to convert fluid files into C++.
However, perhaps you are hand-editing the fluid files? If so, do not do that! The fact that fluid files are *apparently* human-readable is not meant to indicate that they should be human-edited! It is possible, but that is *not* the point. Use the fluid GUI editor to manipulate the files. Don't hand-edit them! If you are determined to hand-edit the fluid files, then your best bet is to use fluid's GUI editor to make small, stand-alone, compileable and testable examples that implement the features you want. Then, for each of these, test the generated C++ to ensure that it does what you want, and if it does, study the fluid files and C++ files to see how that was done. Then copy those features into your hand-edited fluid sources. But... Really, just don't! Use fluid the way it was intended! ******************************************************************** 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

