home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.windows.x:16454 comp.windows.x.motif:6104 comp.windows.x.intrinsics:255
- Path: sparky!uunet!mcsun!Germany.EU.net!Informatik.Uni-Dortmund.DE!heike!klute
- From: klute@heike.informatik.uni-dortmund.de (Rainer Klute)
- Newsgroups: comp.windows.x,comp.windows.x.motif,comp.windows.x.intrinsics
- Subject: Re: Colormap stuff
- Date: 10 Sep 1992 10:06:59 GMT
- Organization: CS Department, Dortmund University, Germany
- Lines: 21
- Sender: klute@heike (Rainer Klute)
- Distribution: world
- Message-ID: <18n6o3INN2df@fbi-news.Informatik.Uni-Dortmund.DE>
- References: <Bu6Jo0.EtD@wpi.WPI.EDU> <1992Sep8.203506.21378@thunder.mcrcim.mcgill.edu> <18lvtbINNbrc@bigboote.WPI.EDU> <1992Sep10.081257.29422@SSD.intel.com>
- NNTP-Posting-Host: heike
- Keywords: color
-
- In article <1992Sep10.081257.29422@SSD.intel.com>, bernhard@ssd.intel.com
- (Bernhard Ries) writes:
- |>For example, if I run ghostscript, the number of
- |> colorcells available for my application is reduced by quite a bit. The
- |> only
- |> way to fix this that I know of is to restart the X-window server.
- |>
- |> Does anybody know what the reason for this behavior is or if there is
- |> any
- |> way to work around it?
-
- I suppose you run Ghostscript via GhostView, right? GhostView by default
- installs a standard colormap, which can be removed by "xstdcmap -delete
- default". There's a GhostView resource to circumvent the standard colormap
- installing.
-
- --
- Dipl.-Inform. Rainer Klute klute@irb.informatik.uni-dortmund.de
- Univ. Dortmund, IRB
- Postfach 500500 |)|/ Tel.: +49 231 755-4663
- D-W4600 Dortmund 50 |\|\ Fax : +49 231 755-2386
-