HDTenEightyP/NetNews huggingface dataset:
From: paul@openage.openage.com (Paul Fischer)
Newsgroups: fj.mail-lists.x-window
Subject: Public Domain Fonts or Font builder needed
Date: 10 Sep 92 04:03:31 GMT
Distribution: fj
Organization: Open Age, Inc.

Date: Wed, 09 Sep 1992 18:34:01 GMT
Message-Id: <1992Sep09.183401.13109@openage.openage.com>
Newsgroups: comp.windows.x,comp.windows.x.motif,biz.sco.general,biz.sco.odt

I am looking for public domain fonts for SCO Open Desktop.  I need these in
large size, 48 points would be OK, bigger is better.  My customer is running
on a Cornerstone dual-page monitor, and needs very large fonts.

He is willing to build them himself, if a PD fontbuilder is available.

His X is R4 under SCO.  If these are available anywhere for anonymous ftp
or UUCP I would appreciate people dropping me a line.

Please send e-mail, as I don't often read news on some groups.

-- 
--------------------------------------------------------------------------------
Independent SCO support and service provider in the D.C. metro area.
What I don't know I will learn. What I can't learn I'll hire someone to.
Paul A. Fischer           | Open Age Inc.  | paul@openage.com
From: jec@cbnews.cb.att.com (john.collier)
Newsgroups: fj.mail-lists.x-window
Subject: Thanks for directions to olvwm 3.0!
Date: 10 Sep 92 05:02:08 GMT
Distribution: fj
Organization: AT&T

Date: Wed, 9 Sep 1992 14:51:28 GMT
Message-Id: <1992Sep9.145128.15102@cbnews.cb.att.com>
Newsgroups: comp.windows.x

Thanks to everyone who told me how to get a new copy of olvwm.  The concensus
was unanimous...ftp it from export.lcs.mit.edu.  I was able to do that and had
to obtain the "patch" program from another site as well.  I have managed to 
build it and presently have it running on my workstation.

Building olvwm was kind of like learning how to swim...it was a lot easier to 
do once I got out of the bag :-)!

Your assistance is greatly appreciated.

-- 
-------------------------------------------------------------------------------
 Working around here is like going into a swamp | John Collier, AT&T Bell Labs
 full of alligators...you'll either be eaten    | ARPA:  jec@cbnea.ATT.COM
 alive or wind up with some really nice luggage!| uucp/e-mail:  att!cbnea!jec
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Questions regarding TVTWM
Date: 11 Sep 92 10:56:46 GMT
Distribution: fj
Organization: McGill Research Centre for Intelligent Machines

Date: Thu, 10 Sep 92 22:49:29 GMT
Message-Id: <1992Sep10.224929.5271@thunder.mcrcim.mcgill.edu>
Newsgroups: comp.windows.x

In article <amoss.715949819@falafel>, amoss@huji.ac.il (Amos Shapira) writes:
[stuff about tvtwm and setting the screen's background]
> What I would really like to have in tvtwm is that it wouldn't obscure
> the real root so no-one should know about it and so I get the same
> image no matter what part of the virtual root is visible currently

This is possible.  The conceptually simplest way of doing it is
probably to do away with the virtual root altogether, and pan by moving
all the windows individually.  I am told this has been tried and it has
unacceptable performance problems.  The next way that occurs to me is
to use the SHAPE extension to shape the pseudo-root window so that it
covers exactly and only those areas that have client windows on them.
I have not heard of this being tried, and no other ways come to mind
immediately.

> (I was thinking while writing this [I sometimes do that :)] and
> though that maybe a transperant window as the virtual root might do
> that? What do you think?)

Sounds nice, but transparent windows don't really exist.  (Well, they
do, but an InputOnly window can't have InputOutput children, so that
solution is out.  *Why* an InputOnly window can't have InputOutput
children I don't know.)  Setting the pseudo-root's background to
ParentRelative would help, but only partially.

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu
From: khamer@sumax.seattleu.edu (Little Kenny Hamer)
Newsgroups: fj.mail-lists.x-window
Subject: Xdtm Makefile now works.
Date: 6 Sep 92 09:26:16 GMT
Distribution: fj
Organization: Seattle University, Seattle, WA

Date: 5 Sep 92 22:11:12 GMT
Message-Id: <4966@sumax.seattleu.edu>
Newsgroups: comp.windows.x,comp.os.linux

Organization: Seattle University, Seattle WA

Thanks for your suggestions.  It seems that, for some reason, some but not
all of the command in the makefile were not properly indented with tabs. 
I just went through and fixed all of that.

Now I just have to hack the code for a while.

-Ken
From: larry@gator.rn.com (Larry Snyder)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Free software and the future of support for Diamond products
Date: 10 Sep 92 04:06:16 GMT
Distribution: fj
Organization: The Gator Public Access Unix Site - 219-289-3745

Date: Wed, 9 Sep 1992 10:18:17 GMT
Message-Id: <BuB3AI.Dzs@gator.rn.com>
Newsgroups: comp.unix.sysv386,comp.windows.x,comp.os.linux,comp.os.mach,comp.unix.bsd

dwex@cbnewsj.cb.att.com (david.e.wexelblat) writes:

>2) One of the nice features of XFree86 (and X386) is the ability to switch
>   resolutions via hot-key.  Kiss that goodby without the clock-select
>   logic

that alone is enough for me to be sold on a server (all other things
being equal of course)..  I can change resolutions on the fly from the
keyboard, from VGA to 1K by 768 in various (configurable) invervals

-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
From: 4carroll_j@spcvxb.spc.edu
Newsgroups: fj.mail-lists.x-window
Subject: XPolyReg.c question
Date: 13 Sep 92 21:51:37 GMT
Distribution: fj
Organization: St. Peter's College, US

Date: 11 Sep 92 16:48:35 GMT
Message-Id: <1992Sep11.124835.3835@spcvxb.spc.edu>
Newsgroups: comp.windows.x


 Hi,

	I am in the process of compiling the X-Windows distribution, and have  a 
 question  about one of the modules XPolyReg.c. In that module there are two 
 definitions that are causing me some difficulties:
 
 #define LARGE_COORDINATE		1000000
 #define SMALL_COORDINATE		-LARGE_COORDINATE
 
	These two constants are  later  assigned  to  integer  varibles.  On  my 
 system, int's are 16-bit values. These int's exist inside a structure named 
 BRESINFO.  The  compiler complains, and generates a warning that says these 
 values have been truncated. Has anyone else encountered  this  problem?  If 
 so, what action have you taken.
 
 Thanks
 Jim C.
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: fj.mail-lists.x-window
Subject: Re: GUIs Considered Harmful
Date: 8 Sep 92 23:30:52 GMT
Distribution: fj
Organization: McGill Research Centre for Intelligent Machines

Date: Tue, 8 Sep 92 19:50:30 GMT
Message-Id: <1992Sep8.195030.18897@thunder.mcrcim.mcgill.edu>
Newsgroups: alt.religion.computers,comp.windows.x,comp.human-factors

In article <RJC.92Sep4141217@daiches.cogsci.ed.ac.uk>, rjc@cogsci.ed.ac.uk (Richard Caley) writes:
> In article <1992Sep3.220451.13791@thunder.mcrcim.mcgill.edu>, der Mouse (dm) writes:
>> Until you use a machine with a trackball, or a tablet-and-puck, or a
>> retinal tracker, instead of a mouse...or if, as I suspect, xcal
>> doesn't bother to check and blindly assumes a three-button mouse,
>> you use it with a mouse with other than three buttons.

> Gee, isn't all the world a Sun? :-)

Everyone sure seems to assume so.  Blindly assuming three-button mice
(or indeed assuming the pointer device is a mouse at all), blindly
assuming everything of depth greater than 1 is depth-8 PseudoColor....
Grrr.

> Actually, while mutant mice with less than three butons exist, I
> don't think software should cater to this perversion without the user
> providing a 20 page essay on why they are inflicting such a
> monstrosity on the world.

I said other than three buttons, not fewer than three buttons.

And I didn't say cater to.  Printing a message like "I can't run on a
server with only 2 buttons on the pointer" and dying is better than
running crippled due to needing a nonexistent third button.  (Usually.
I would want any such program to have a switch saying "I know what I'm
doing; run anyway.".)  Not checking and then depending on the presence
of those buttons is IMO a bug.

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu
From: perry@sun1.coe.ttu.edu (Dr. Matt Perry)
Newsgroups: fj.mail-lists.x-window
Subject: XVision Problems --- Ooop Ack!!!!!
Date: 11 Sep 92 23:55:34 GMT
Distribution: fj
Organization: Texas Tech University

Date: Fri, 11 Sep 1992 02:15:38 GMT
Message-Id: <1992Sep11.021538.29430@ctr.columbia.edu>
Newsgroups: comp.windows.x

Hi,

I have been having trouble running some X11R4 clients in VisionWare's
XVision package.  I have been in contact with Unipress (Visionware's
US tech support) for THREE weeks now and have gotten nowhere.  I need
to run some of these clients on my PC as our limited sun terminals
are busy with students.

My problem is that when I run clients that use lots of colors there
is an error message from FTP's TCP/IP ddl talking about buffers or some
damn thing.  If the real Visionware people are reading this how about
getting on this and try and help me.  The support I feel I have 
received for the monies spent is certainly not appropriate.  Three
weeks may not seem like a lot to you but when you have work waiting
on your software it is alot of time.

Other pertinent info, these clients ran just fine under Windows 3.0 
and no I cannot switch back.  As an example I cannot run xgif with
the earth.gif file found in archives (255 colors).

Let's here from the real Visionware people that I know exist.

Thanks

Matt Perry

-- 
------------------------------------------------------------------------
Matt Perry, PhD                      Electrical Engineering
Assistant Professor                  Texas Tech
Voice: (806) 742-3489                Box 43102
e-mail: perry@sun1.coe.ttu.edu       Lubbock, TX, USA  79509-3102
------------------------------------------------------------------------
From: hecht@theory.TC.Cornell.EDU (Caroline Hecht)
Newsgroups: fj.mail-lists.x-window
Subject: "Unknown keysym name" warnings
Date: 13 Sep 92 09:05:19 GMT
Distribution: fj
Organization: Cornell National Supercomputer Facility

Date: 11 Sep 92 18:09:28 GMT
Message-Id: <1992Sep11.180928.29040@tc.cornell.edu>
Newsgroups: comp.windows.x

I built X11R5 for our AIX/370 system.  When I run the standard
clients, I get numerous warnings about unknown keysym names.  The
XKeysymDB file is in place at runtime, although it didn't exist when I
ran "make World".  Is the XKeysymDB file required to be there at build
time?  Does anyone have an idea what is causing these warnings?  Here
are the warnings I get from xterm and xclipboard, for example:

$ xterm
Warning: translation table syntax error: Unknown keysym name: Select
Warning: ... found while parsing 'Shift <KeyPress> Select:select-cursor-start() select-cursor-end(PRIMARY, CUT_BUFFER0) '

$ xclipboard
Warning: translation table syntax error: Unknown keysym name: BackSpace
Warning: ... found while parsing '~Shift Meta<Key>BackSpace:    delete-previous-word() '
Warning: translation table syntax error: Unknown keysym name: BackSpace
Warning: ... found while parsing ' Shift Meta<Key>BackSpace:    backward-kill-word() '
Warning: translation table syntax error: Unknown keysym name: BackSpace
Warning: ... found while parsing '<Key>BackSpace:       delete-previous-character() '

Please respond by e-mail.

Thanks,
Caroline Hecht

--
Caroline Hecht        hecht@tc.cornell.edu        (607) 254-8686
Cornell Theory Center / Cornell National Supercomputer Facility
743 ETC   /   Cornell University   /   Ithaca, NY 14853
From: oj@miki.pictel.com (Oliver Jones)
Newsgroups: fj.mail-lists.x-window
Subject: Re: can an R5 client connect to R4 server?
Date: 8 Sep 92 19:42:24 GMT
Distribution: fj
Organization: PictureTel Corporation

Date: 8 Sep 92 13:04:15 GMT
Message-Id: <1992Sep8.130415.2471@miki.pictel.com>
Newsgroups: comp.windows.x

In article <1992Sep7.201706.3675@ilinx.wimsey.bc.ca> brian@ilinx.wimsey.bc.ca (Brian J. Murrell") writes:


>I just compiled X11R5 on one
>of the machines in my office.  

OK, let's say you compiled the X11R5 CLIENTS on your host system.
(You may have complied the server too, but that's irrelevant to the
problem at hand.)

>I have two other machines running
>R4 (a SVR4 workstation, and a PC running an R4 server under MS
>Windows).  

OK, let's say your SVR4 box and your PC are running X11R4 SERVERS.
It's possible they are running clients locally, too -- again,
irrelevant.

>I can't seem to start any applications on my R5 system
>with the -display set to either workstation.  

OK, let's say you cannot launch any X11R5 client from your host
system to connect to the SVR4 box or the PC.

If my clarifications don't describe your situation correctly,
then maybe you should repost with a more accurate description of
your trouble.

>I get an error message such as below if I try to start any client
>with the parameter -display ilinx:0.0
>Error: Can't open display: ilinx:0.0

This could be anything.  I get this when I unplug my ethernet,
or mistype the hostname of the X server.  Are there any other messages
with it.

Now, the questions.  

Can you launch ANY X clients (R4, R3, ...) from your host system to
connect to the PC or SV box? Try a simple one like xdpyinfo.  If you
can launch an OLD client, but not an R5 client, then you have a fairly
good idea that something's wrong with R5.  But, I doubt it.

Can you ping the PC or SV (are the TCP stacks working throughout)?

If your host system is a Sun, try using the trace command to see what system
calls it's making.





>I get an error message such as below if I try to start any client
>with the parameter -display ilinx:0.0 > >Error: Can't open display:
ilinx:0.0 > >So what's the story here??  > >brian >-- >Brian J.
Murrell brian@ilinx.wimsey.bc.ca >InterLinx Support Services, Inc.
uunet!van-bc!ilinx!brian >North Vancouver, B.C.  > Platform and Brand
Independent UNIX Support - R3.2 - R4 - BSD
From: snail@lsl.co.uk
Newsgroups: fj.mail-lists.x-window
Subject: GUIs Considered Harmful (Different Distribution)
Date: 7 Sep 92 18:32:50 GMT
Distribution: fj
Organization: Laser-Scan Ltd., Cambridge

Date: 7 Sep 92 17:11:51 GMT
Message-Id: <1992Sep7.181151.2402@lsl.co.uk>
Newsgroups: comp.windows.x

Aargh!

This thread is driving me mad! Why? 'Cos I want to be involved but our
newsreader barfs (I hate that word) at the first newsgroup
(alt.religion.computers) and I can't followup as a result (please remove this
group from the followup postings.. PLEASE) so I've resorted to this.

So I agree with the chrome arguments

BUT OPENLOOK stinks... no sideways or vertical resize - you've gotta grab a
corner -bleugh!

The thing that got me was a person slagging DECs weirdness - well I won't
defend that, but he didn't slag Sun, who've easily got the worst keyboard
layout after HP (ever used a 700 series - dead flesh Clive Sinclair Keyboard
feel PLUS a very strange key placement policy) and Sun a workstation keyboard
that doesn't even have separate keys (I believe fixed with Type 5 keyboards -
but have yet to see) for cursor control - and all the other keys are in odd 
places. At least DECs keyboard is close to that of an (blasphemy alert) IBM PC,
the keyboards on RS/6000s are PC compatible but so cheap its unbelievable -

I mean HP and IBM keyboards feel like toys cheap and plasticy and tacky and
yet its on eqiupment that costs thousands of pounds. My parent's PC keyboard
has much better reponse and feel (and I bet in Taiwan it only cost #10 or
less to build)

OOPs - I got off the thread slightly, bet I'll get hate mail from HP etc, but
VUE is excellent. I can't remember some of teh other argumnets right now,
but GUI is great for somethings, but CLI better for other and you NEVER have
it any other way, but if you're gonna go on about Emacs meta-x-cokebottle-tops
and TECO (I last saw in '84?) and slag off C++ and sensible design then I'm 
gonna disagree - Emacs is great and so is Brief (IBM PC world - its an editor)

Sayonara

snail@lsl.co.uk



-- 
snail@lsl.co.uk      

Interviewer: "What's the most satisfying thing about being in
              The Sisters Of Mercy?"
Eldritch:    "When I collapse at the end of it..."
Interviewer: "Do you mean that?"
Eldritch:    "Yeah...."

Vote for Bill Clinton. Vote for Bill Clinton. Vote for Bill Clinton.
From: veck@pshrink.chi.il.us (Steve King)
Newsgroups: fj.mail-lists.x-window
Subject: Re: GUIs Considered Harmful
Date: 10 Sep 92 23:29:52 GMT
Distribution: fj
Organization: PShrink Wrap BBS, Lake Zurich IL  +1 708 540 6772

Date: Tue, 08 Sep 92 18:17:54 CST
Message-Id: <Jc6sqB1w165w@pshrink.chi.il.us>
Newsgroups: alt.folklore.computers,comp.windows.misc,comp.windows.x,comp.human-factors

adrian@milton.u.washington.edu (Adrian Mariano) writes:
>The problem with the mice that use the LEDs and reflective mouse pads
>is that you must use the mouse pad, and you MUST have it oriented
>correctly.  If you turn it 90 degrees, the mouse won't work.  If the
>mouse pad gets rotated, then the mouse won't do what you want (or
>expect).  

Not so with the newer Mouse Systems critters.  The one I've got here
works equally well at any 90 degree orientation.  You must still, of
course, manage to keep it on the pad.  I've always thought you could make
a lot of money by producing rolls of mylar shelf paper that have a mouse
tracking grid printed on it...  :-)

I've got a feeling that the optical versus mechanic mouse battle is
the sort of holy war usually left for discussions of EMACS versus VI.


-- 
Steve King (veck@pshrink.chi.il.us)
PShrink Wrap BBS, Lake Zurich IL  +1 708 540 6772
From: jrutledg@cs.ulowell.edu (John Lawrence Rutledge)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Colormap stuff
Date: 11 Sep 92 01:53:52 GMT
Distribution: fj
Organization: Interactive Media Group - University of Massachusetts at Lowell

Date: Thu, 10 Sep 1992 14:13:47 GMT
Message-Id: <1992Sep10.141347.390@ulowell.ulowell.edu>
Newsgroups: comp.windows.x,comp.windows.x.motif,comp.windows.x.intrinsics

In article <18lvtbINNbrc@bigboote.WPI.EDU>, rtipnis@cs.wpi.edu (Rajeev Tipnis) writes:
-> SetupMyColormap()
-> {
	.
	. (deleted for space)
	.
-> 	/* Install this colormap for this display */
-> 	XInstallColormap(dpy, my_cmap); 
-> 	
-> }

	A client program should never call XInstallColormap(), it is
the job of the window manager.  The only time it should be called is if the
program knows there is no window manager running.  If there is window manager
running, it may even immediately uninstall the colormap (twm does this).
The proper why to use your own colormap is to create the top level window(s)
of the application with the colormap.  In the X Toolkit just set the 
colormap resource of all the shell widgets.

-- 
+-----------------------------+-----------------------------------------------+
|			      |  "If only it were a modern document, with a   |
| John Lawrence Rutledge      | smart index and hyper links stretching all    |
| Research Assistant	      | through the world data net.  It was terribly  |
| 			      | frustrating to flip back and forth between    |
| Interactive Media Group     | the pages and crude flat illustrations that   |
| Computer Science Department | never even moved.  Nor were there animated    |
| U of Mass - Lowell          | arrows or zoom-ins.  It completely lacked a   |
| 1 University Ave.	      | for sound.                                    |
| Lowell, MA 01854            |  "Most baffling of all was the problem of new |
|			      | words...  In normal text you'd only have to   |
| (508) 934-3611	      | touch an unfamiliar word and the definition   |
| jrutledg@cs.ulowell.edu     | would pop up just below."                     |
|			      |    	           from David Brin's "Earth"  |
+-----------------------------+-----------------------------------------------+
From: steve@nuchat.sccsi.com (Steve Nuchia)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Free software and the future of support for Diamond products
Date: 13 Sep 92 21:55:24 GMT
Distribution: fj
Organization: South Coast Computing Services, Inc.  Houston

Date: 13 Sep 92 14:20:36 GMT
Message-Id: <1992Sep13.142036.26842@nuchat.sccsi.com>
Newsgroups: comp.unix.sysv386,comp.windows.x,comp.os.linux,comp.unix.bsd,comp.os.mach,comp.sys.ibm.pc.misc,comp.sys.ibm.pc.hardware

In <1992Sep12.035549.4743@zeos.com> kgermann@zeos.com (Ken Germann) writes:
>The solution for the support of X/Windows in the Freeware arena or
>any other arena would be to design a VESA based driver for these

The solution, for those of us who care about such things, is to
not buy undocumented hardware.  Vote with your wallet.
-- 
Steve Nuchia      South Coast Computing Services, Inc.      (713) 661-3301
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: fj.mail-lists.x-window
Subject: Re: keysymdef.h, Why it is defined that way?
Date: 8 Sep 92 11:26:34 GMT
Distribution: fj
Organization: McGill Research Centre for Intelligent Machines

Date: Tue, 8 Sep 92 08:56:14 GMT
Message-Id: <1992Sep8.085614.13917@thunder.mcrcim.mcgill.edu>
Newsgroups: comp.windows.x

In article <1992Sep1.035254.14586@cbnewsl.cb.att.com>, noname@cbnewsl.cb.att.com (  ) writes:

> In the "keysymdef.h" file, the data looks like this:

> #define XK_space	0x020
[...]
> #define XK_asciitilde	0x07e
>                                 <---- please note the blank line here. 
> #define XK_nobreakspace	0x0a0
> #define XK_exclamdown	0x0a1
[...]

> My question is:

> Is there any particular reason that jump the keysym code definition
> from 0x07e to 0x0a0?

Yes.  It makes conversion from KeySyms to ISO Latin-1 a *lot* easier.
(In fact, it's the identity transformation.)

The blank line has no semantics in C terms and is almost certainly to
improve human readability.

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu
From: rtipnis@maxine.WPI.EDU (Rajeev Tipnis)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Colormap stuff
Date: 10 Sep 92 14:12:19 GMT
Distribution: fj
Organization: Worcester Polytechnic Institute

Date: 9 Sep 1992 23:04:11 GMT
Message-Id: <18lvtbINNbrc@bigboote.WPI.EDU>
Newsgroups: comp.windows.x,comp.windows.x.motif,comp.windows.x.intrinsics

	Thanks to all those who sent me mail or followed up to 
	my posting on "how to change the colormap cells on the 
	fly".

	I am including some code here, which lets the programmer
	figure, how not to touch the color cells of the colormap
	which are getting used by other applications on the same
	display, and use the rest of the colormap. 
	
	Thanks again for all your help.


SetupMyColormap()
{
	int	i;

	unsigned long 	cells[MAXCOLORS], got[MAXCOLORS];
	ncells = MAXCOLORS;

	/* get the default colormap */
	dmap = DefaultColormap(dpy, DefaultScreen(dpy));


        /* Initializes the XColor structure to represent each color cell
	   in the default colormap */
	for (i=0; i<MAXCOLORS; i++) {
		Colors[i].pixel = i;
		Colors[i].flags = DoRed | DoGreen | DoBlue;
	}
	/* Query into the default colormap, to get the default colors */
        /* loads the color component of the Xcolor structure  */	
	XQueryColors(dpy, dmap, Colors, MAXCOLORS);

	/* Allocate the read-write color cells. This function is used to 
	   figure out which all cells of the defaultcolormap are already
	   allocated. ncells is decremented to get the count of the
	   remaining cells and cells array gets the pixel number of the
	   color cells which were free for this allocation */
	while (XAllocColorCells(dpy, dmap, True, NULL, 0, cells, ncells) == 0) 
 	 	ncells--; 

	/* create your own colormap, so that (u can read and write into
	   it) and also allocate all the cells */
	my_cmap = 
		XCreateColormap(dpy, DefaultRootWindow(dpy),
				DefaultVisual(dpy, DefaultScreen(dpy)),
				AllocAll);

	/* Fill those Xcolor structure elements which correspond to the
	   unallocated cells, with whatever colors u want */ 

	/* store this Xcolor structure array into your colormap */
	XStoreColors(dpy, my_cmap, Colors, MAXCOLORS);

	/* Install this colormap for this display */
	XInstallColormap(dpy, my_cmap); 
	
}