From: Virgil W. <vir...@ra...> - 2000-03-17 00:57:29
|
> Dear Virgil, > > for me - personally - it is too early for trying win2k ! > > But thankxs for your bug-finding ! > > So we have to locate the bug, is it a : > 1) GL4Java Bug > 2) OPENGL32.DLL Bug > 3) a ICD OpenGL driver BUG > ! > > Anyway, I we can remove those printouts outta the native libraries, > or can only print em out, if native debug is set to true ! > > Well, the next version will implement this ... > > Is this "feature" really needed now ? Just making the prints conditional on debug mode is probably good enough for the short term. As is, it's nearly impossible to do any println debugging from my own code. I remember looking into this problem several months ago when I first looked at gl4java. At the time I didn't learn much about the problem (other than where in the native code the prints come from and that the call that causes them to be printed shouldn't be "failing".) As for windows 2000, I've had good experiences with it so far. I've used NT4 a lot and windows 98 a good bit as well. The only problems I've had with 2000 so far are trying to use direct3d (using the microsoft vm's jdirect interfaces) in full screen mode. The results aren't very pretty... Speaking of full screen mode (and not to intentionally change the subject:), but can full screen mode be supported with gl4java? Applets are nice, but if a person were to write something like a "real" game they'd want fullscreen support (so folks can do things like bump the edge of the screen to scroll across the game space). Thanks for you feedback, Virgil Wall vir...@ra... Director, R&D Hummingbird Raleigh, NC http://www.hummingbird.com |