Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!RELAY.PROTEON.COM!Osman_Ahmad_at_CTC From: Osman_Ahmad_at_CTC@RELAY.PROTEON.COM Newsgroups: comp.sys.apollo Subject: Re: Motif Problems Message-ID: <9102261624.AA07200@monk.proteon.com> Date: 26 Feb 91 03:40:00 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: Proteon, Inc., Westborough, MA 01581 [(508)898-2800] Lines: 44 > As soon as we start up mwm and try to run the very same program, we > get a fail request (X_QueryColor). >For what its worth, mwm (the 3D look) tends to use more colors than uwm >would need. Also, I believe uwm doesn't install colormaps on behalf of >the client, whereas mwm does. Maybe under uwm you're always querying >the same non-complaining colormap, and under mwm you're having problems >with the changing colormaps. Tom has the correct diagnosis of the problem. We ran into this problem not too long ago. I do not claim to be an X-pert, but here are some solutions and non-solutions we came up with: 1. Do not run Motif(R). Is it really worth it? Does twm offer an alternative? 2. Get X-displays with 256 colors instead of 16. We noticed that Motif(R) will gobble up 14 colors (it allocates them in shared mode so you will get lucky with some applications, especially if they do not use colors!). With a 256 color display, we do not have a problem. 3. If you have access to your applications source code, you should be able to install your own color maps. Motif(R) and other ICCCM compliant window managers will do wonders with false colors as you move your focus from one window to another. Let me know if you need any details re: the third option. Visually, it is not very impressive but it works. /Osman Osman_Ahmad_at_CTC@relay.proteon.com Association of American Railroads Chicago Technical Center (312) 567-6751 compliant window managers convert the program Brought to you by Super Global Mega Corp .com