Article View: comp.windows.x
Article #38050Re: Xt and non-default visuals (e.g. X/News PseudoColor)
From: Steve Jacobson
Date: Wed, 14 Mar 1990 00:58
Date: Wed, 14 Mar 1990 00:58
12 lines
1044 bytes
1044 bytes
Here's some further comments about the problem described in the previous posting. I remember doing some testing with the MIT server where a Shell widget created with a read/write colormap did not result in the protocol error, but instead in the "cannot allocate color entry" warning that you would expect (but maybe not desire). The difference between the two situations is the visual - default for the MIT, and non-default for X/News. Any insight into this problem will be appreciated.
Technical Details
Message-ID:
<1990Mar14.005821.16829@agate.berkeley.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!agate!garnet.berkeley.edu!csvsjReferences:
<1990Mar14.004423.16114@agate.berkeley.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!agate!garnet.berkeley.edu!csvsj From: csvsj@garnet.berkeley.edu (Steve Jacobson) Newsgroups: comp.windows.x Subject: Re: Xt and non-default visuals (e.g. X/News PseudoColor) Message-ID: <1990Mar14.005821.16829@agate.berkeley.edu> Date: 14 Mar 90 00:58:21 GMT References: <1990Mar14.004423.16114@agate.berkeley.edu> Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44) Organization: University of California, Berkeley Lines: 12