> Actually as demonstrated inhouse it is possible to have a printer installed
>incorrectly
> and have some functions cause AVs but not others... EG a lookup into the
>Printer.Fonts
> list caused an AV even though Word could print fine...
> For a professional app all resource accesses that can throw an exception should
> have their relevent handlers and resource protection blocks...
I've considered writing a polymorphic "TOutputDevice" class which
provides information about a printed page. If a default printer exists
and is working correctly, the information will be returned from that,
otherwise there'll be like a 'default' device with A4 paper, 360 dpi,
etc. Comments?
- Matt
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
