Klas,
I imagine I'll have to maintain a static variable for each of the
non-output
functions and include the codes in subsequent (with output) function
calls.
Thanks for your replay.
Regards,
Gary
"Klas Engwall" <klas.engwall@[EMAIL PROTECTED]
> wrote in message
news:47c8a4d6$0$1340$834e42db@[EMAIL PROTECTED]
> Gary,
>
>>I need to remove Esc40 from my Clipper app and replace the Esc40
functions
>>i.e. hpCenter(), hpAtSay() ... with their underlying hp equivalents.
Most
>>of the functions are easily reversed engineered by simply sending the
>>output
>>to a file; however, setup functions like hpUnits() and hpPhysical()
don't
>>have any output. Has anyone tried to remove Esc40 or have any
>>recommendations?
>
> What does the manual say about those functions? It sounds like they
> set some static variables for the page setup in the Esc40 runtime. If
> you create a small test application that draws a box, for example, and
> vary the settings in hpUnits() and hpPhysical() between the runs you
> should see different escape sequences being output to your file. Then
> look those up in the PCL Technical Reference.
>
> Regards,
> Klas
>
> -------
> klas dot engwall at engwall dot com
>
> http://www.engwall.com/clipper/
>
> The LFN Library for Clipper
> The LanMan Library for Clipper
> The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
