🚀 go-pugleaf

In article <edh.723936953@staff.tc.umn.edu>, edh@staff.tc.umn.edu (Eric D. Hendrickson) writes:
|> I have a procedure for dynamically creating a Color * from a set of RGB
|> values.  On Suns, I keep running out of colors.  I have tried to display it
|> on an SGI, but it doesn't get any more colors.  I am not physically running
|> the program on either the Sun or the SGI, but on a faster MIPS machine.
|> 
|> I can't run the program on the SGI directly as there is no g++ compiler,
|> but my understanding is that only the display matters as far as color
|> allocation goes.
|> 
|> I'm using InterViews 2.6 and g++ 2.3.1.
|> 
|> Thanks!
|> 		--eric
|> -- 
|> 			   "'Wit smoke and fire and fumes an' what-not comin'
|> 			    outta dere nostrils... dey rep'esent youah
|> 			    virility... Likewise wit' d'enormous bulge in
|> 			    y'pants here."

What you could do here is create a colour catalog.  Wach time you want a color ask your catalog to give it to you.  The catalog can maintain a list of colors that it has already created and if a color that has already been created is requested then that colour can be passed back.  If the color does not exist then it can be created, added to the list and then passed back.

This would avoid the need to create duplicate colors.  You would probably need to add some persistence to your colour objects to avoid problems caused by an object deleting a colour that another object is still using.

Nathan