Hi Andrew,
I have encounted the same problem. ITs the same problem with
byte transparency !! Well, i really dont understand how "byte" colors,
xparency works and after getting frustrated with it, i switched to float.
here is the deal, maybe im wrong (im pretty much a newbie)
-In java, byte stores values from -128 to 127
-I dont know if there is a byte primitive such as "unsigned byte"
-so if you give color>127b, to a byte varible, it performs wierd.
Gurus, please let me know where im wrong. i had orinally thaught that the
problem is with my card, but things started to work fine after i
switched to float from byte. i suggest you do too
-aditya
On Thu, 22 Jul 1999, Andrew R. Thomas-Cramer wrote:
>
> In a GeometryInfo object, if I setColors3(byte[]), values above 127 don't seem to
>appear. Values from 0-127 do. But RGB colors are represented by a 3-tuple each of
>whose components are in the range [0,255].
> I didn't see this in Sun's list of bugs.
> Has anyone else encountered this behavior?
> If this is a bug in the library rather than my application, could it be related to
>Java's inability to represent logically unsigned values as physically unsigned types?
>
> ================================================================================
> Andrew R. Thomas-Cramer
> Home: [EMAIL PROTECTED] http://www.execpc.com/~artc/
> Work: [EMAIL PROTECTED] 608.287.1043
>
> "Your quote here."
> -- Bjarne Stroustrup, "The C++ programming language," chapter 13: "Templates".
> ================================================================================
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
