[softwarelist] Re: OPro 2.76

In message <510c8a914e.martin@xxxxxxxxxxxxxxxxxxx>, Martin Wuerthner <public@xxxxxxxxxxxxxxx> writes 
Yes. Things would go horribly wrong if SpecialFX redirected Draw calls
to GDraw when printing. GDraw can only print correctly if it is hooked
into the printing system in precisely the right way - ArtWorks-aware
apps ensure that by calling AWRender_ClaimVectors at the right moment.
GDraw would not work with any old app that prints.
Using what you discovered i.e. setting Sprinter to high resolution I have reproduced the problem. It seems the original document is corrupt - that is the document generated by loading the Impression document. It is interesting that corruption occurs at such an early stage.
I'm inclined to think fixing what causes the corruption would fix the strange rendering command. 


--
David Pilling
email: david@xxxxxxxxxxxxxxxxxxx
  web: http://www.davidpilling.net
 post: David Pilling P.O. Box 22 Thornton Cleveleys Blackpool. FY5 1LR UK
  fax: +44(0)870-0520-941

Other related posts: