At someone else's request, I made the slight modification to the WinFlex source (and compiled it) so that:
You can get the updated winflex.exe from: ftp://ftp.morningstar.com/pub/tools/windows/. The full source, including an VC++ project file, is available in the same directory as ftp://ftp.morningstar.com/pub/tools/windows/winflex-src.zip.
PLEASE do not email me about this software. If you have any questions, send them to the HylaFax mailing list, where they are more likely to be read by somebody who has the time to read and answer them.
I provide this with no warranty, no offer of help if it doesn't work the way you want it to, and request that nobody deluge me with a list of requests for things to change in WinFlex - I don't have the time or the desire to do that.
The changes:
show()to:
show(SW_MINIMIZE); show(SW_RESTORE);
writeLine("pagelength", dp->pLen);add the line:
writeLine("notify","when done");
Also, someone from Denmark requested a version that doesn't have the
papersize hardwired to be US Letter, and that is in
winflexa4.zip.
....
I did this on purpose because something in the combination of the
Windows PS driver + GhostScript caused the aspect ratio of the page to
be "nailed down" so that when gs was told to output as A4 (slightly
longer and narrower than US Letter), the Windows-generated PS file would
end up being (if I remember the number correctly) 4 pixels too wide for
Hylafax to send as a fax (but hey, it *was* . After several people
looked at this (ie at the ps files) and concluded that "it shouldn't
happen, but I can't see what's wrong", I decided to prevent anyone from
sending a fax that only contained a single error message line (and
nothing else) by hardwiring the page size to be US Letter (even if you
change the radio control, it still sends it letter size, since A4 is
always doomed to failure anyway).
[added by the FAQ maintainer: see also
Q: Problems while sending a PS document... for this problem.]
....
I sure wish someone would port WinFlex to MFC so that anybody with VC++
could build it, rather than the whole world having to rely on the
goodwill of the few of us who have zApp - I'm sure that would make for
much more development of new features on the program. It really
shouldn't be too much trouble doing so either, since the user interface
is just 4 dialogs and an About box (and the main window which is used by
the logger class), and all the rest could be moved over with basically
no changes (the socket library doesn't need zApp) - the only trick to it
is the handling of the WM_SPOOLERSTATUS message (that's how the Windows
Print Manager notifies WinFlex that there is a file available to
"print").
....
I think an MFC version of WinFlex would be a valuable addition to the
suite of HylaFax support programs, and hope that somebody with the time
to do it is lurking in the wings looking for a project to jump on.
Matthias Apitz / guru@softcon.de ; (07:34:58 AM 01/27/97)