[comp.windows.open-look] that !!@#$#@ color problem

weisberg@ee.rochester.edu (Jeff Weisberg) (04/07/91)

>>  Recently I posted a request for help with XView colormap segments.  As it
>>turned out, the problem was not one with my colormap segment, but with the
>>server image that I was using to test it.  Which led me to an entirely
>>different dilemma:
<...>

>A Sun guy I've talked to seems to think it's a server image problem and 
>has alerted the Xview engineers. It sure looks like a signed problem!
>This problem probably will be fixed in OW 3.0.

 I too just ran into this 128 max. color problem. If this a bug, anyone
come up with a way around it. 128 colors just isn't going to cut it 
I need to be able to use all 256.
	Thanks for any help,
	Jeff Weisberg
	weisberg@ee.rochester.edu

courtney@arirang.cps.msu.edu (Jonathan Courtney) (04/09/91)

  I think I might have found a fix for our server image problem.  Apparently,
xv_create calls to make server images objects zero out the input data before
it stores it in its internal pixmap.  So the solution is to bypass the data
processing phase, right?

  The Solution:  Create an XImage of the data you wish to display.  Write
this image with XPutImage to a pixmap that you create of the same size.
Then use this pixmap as the input to the server image create call, as
such:

  image = xv_create(NULL, SERVER_IMAGE,
			SERVER_IMAGE_PIXMAP, pixmap,
			NULL);


  Believe it or not, this works.  Unfortunately, it is only useful if you
are restricted to use only server image types instead of an XImage.  In my
case, I can't use an XImage because I am trying to use the data as part of
an XView list object.

						Jon Courtney