| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 1772.1 | Difference between definition and capability | MELTIN::dick | Gvriel::Schoeller | Mon Nov 20 1989 19:32 | 7 | 
|  | The value of a named color is described by a set of RGB information
(in logicals on VMS).  This information may be in a format with more
significant digits than the display you are on.  Therefore, you get
a returned value in the screen color that is slightly (sometimes
substantially) different than the exact color.
Dick
 | 
| 1772.2 | That's not the problem | EPIK::J_JOSEPH | Living in the Pasture | Tue Nov 21 1989 11:15 | 11 | 
|  | >The value of a named color is described by a set of RGB information
>(in logicals on VMS).  This information may be in a format with more
>significant digits than the display you are on.  Therefore, you get
>a returned value in the screen color that is slightly (sometimes
>substantially) different than the exact color.
The thing is, if you do an XAllocColor, you can get precisely the RGB values
described in the file DECW$RGB.COM.  Why should XAllocNamedColor give you 
anything different if you *CAN* get the exact values described?
-Jonathan
 | 
| 1772.3 | That still may be the issue | GVRIEL::SCHOELLER | Who's on first? | Tue Nov 21 1989 11:49 | 9 | 
|  | >The thing is, if you do an XAllocColor, you can get precisely the RGB values
>described in the file DECW$RGB.COM.  Why should XAllocNamedColor give you 
>anything different if you *CAN* get the exact values described?
If you XAllocColor with the RGB returned in XAllocNamedColor's
exact value.  Do you get that RGB or the one returned in the screen
value?
Dick
 |