Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!bu.edu!att!cbnewsc!tjr
From: tjr@cbnewsc.att.com (thomas.j.roberts)
Newsgroups: comp.lang.c
Subject: Re: Turbo C graphics on a PC
Message-ID: <1990Nov16.160420.22339@cbnewsc.att.com>
Date: 16 Nov 90 16:04:20 GMT
References: <11203@ccncsu.ColoState.EDU>
Organization: AT&T Bell Laboratories
Lines: 21

From article <11203@ccncsu.ColoState.EDU>, by ss746724@longs.LANCE.ColoState.EDU (Steve):
> C users:
> 
> [...] Eventually I would like to be able to print the resulting
> graphic to a laser jet. [...]

This is a MAJOR failing of Turbo C graphics - there is ABSOLUTELY
NO PRINTER SUPPORT. It works fine on a multitude of display hardware.

In principle, BGI drivers could be written for printers, but the
BGI interface DOES NOT provide all of the necessary hooks [e.g.
drawing to printer, but putting menus on screen, using different
fonts for printer and screen, etc.]

Before Turbo C, I used my own graphics library, specific to by own
devices. What I have done is modified it to use Turbo C graphics
for the screen, but to use its internal routines for the printer.
This is a cumbersome and un-general way to do it, but it works.

Tom Roberts
att!ihlpl!tjrob