On 03.03.2010 at 11:20, manolo gouy wrote: > Albrecht: How to connect your work with the existing code: > > All should go into member functions > Fl_PS_Printer::start_job() and Fl_PS_Printer::end_job() > at the very end of the (too big) file src/Fl_PS_Printer.cxx > > I have commented these to clarify what to transmit, under the > expectation that a temporary PostScript file name would be exchanged. > If it's more convenient for you to transmit a FILE * (e.g., pipe, or > close on delete) you will have to change things a little bit more. > > But you may know that already by now.
Yup, but thanks anyway. Currently the dialog pops up, I can select options, but then I let it fall back to the PS output. The fluid implementation doesn't create a file for printing, but pipes the output directly into the lp command. I think that I'll keep that, but then I'll have to modify the close command at the end of the print job. I'll probably have to add a new member variable somewhere in the Fl_Printer class(es), but that's the next step. Currently I'm restructuring the code (to get rid of global variables), but the final solution will probably be an own class for better handling. I'll commit a temporary solution, however, as soon as I can print successfully. The rest can be done in a second step. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
