Around 16 o'clock on Sep 15, Mark Vojkovich wrote:

>    Like by temporarily lowering the sigBits?  Changing current allocation
> behavior makes me uneasy.  Doesn't the specification say something
> about this?

AllocColor:

"This request allocates a read-only colormap entry corresponding to the
 closest RGB values provided by the hardware. It also returns the pixel and
 the RGB values actually used. Multiple clients requesting the same
 effective RGB values can be assigned the same read-only entry, allowing
 entries to be shared."

This has always been interpreted to say that PseudoColor allocations 
return the best possible color and fail if no exactly matching cell is 
available.  And, I'm sure rws would concur that this was the intent.

However, we might consider stretching this to allow matching of existing 
entries that were not precisely the same as the requested value as a way 
to avoid application failure or flashing.  This is what StaticColor 
visuals already do, so it's not as if we'd be breaking new ground here.

The server could allocate a set of fixed colors that would be used to 
match all read-only requests; read-write requests would use the remainder 
of the colormap.  That seems like it would give applications the benefits 
of PseudoColor visuals while forcing other applications to share the 
available read-only cells better than they do today.

It would be easy to do; just make read-only allocations from clients match 
existing read-only cells in the colormap, then let the Render extension 
build the read-only cells and you're all set.

> Besides the quality will drop noticeable.

Yes, applications allocating read-only colors will see a significant 
reduction in fidelity. Those same applications usually have an option to 
create their own private colormap, in which case they'll have complete 
access to the available hardware capabilities.

> How about a config file option for the size of Render's color cube?

That's my plan; just specify the maximum number of colors available to 
Render in the config file and make it suffer.  When presented with 0 
colors, it should disable itself.

[EMAIL PROTECTED]        XFree86 Core Team              SuSE, Inc.


_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert

Reply via email to