Date: Sat, 15 Jun 2002 11:29:44 +0300 (WET) From: Andris Pavenis X-Sender: pavenis AT ieva06 To: Alex Oleynikov Cc: djgpp AT delorie DOT com Subject: Re: GRX printing library In-Reply-To: <4etO8.17654$hF5.636479@news2.east.cox.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Fri, 14 Jun 2002, Alex Oleynikov wrote: > Hi everybody, > > I've got a question on using the printing library which comes as a > contributed package to the GRX library. > It looks like when this printing library is used it invalidates the current > device driver of the GRX and creates a new "memory" driver to do printing. > The simple program to test printing that comes with the library works OK, > since there are no other programs using GRX at that moment, but if you try > to invoke printing routines from a GUI environment residing on GRX it > immediately crashes (I use MGUI with VESA driver, but I think any other GUI > would behave similarly, when its primary driver is gone). > Is there a way to have multiple device drivers in GRX simultaneously , so > using one does not affect others? Unfortunatelly not now. Initially I wanted to have the same printing support I had with ancient Borland C++ 3.1 and printer BGI driver from Ulrich von Bassevitz, therefore I asked him for sources and used some parts of them to write GRX printing support. As far as I remember there were limitation that one cannot have GRX context with different depth simultaneusly. Printing support in GRX is rather ugly hack and I don't have plans to do anything there in nearest future. Andris