> That's our fault. The spec only added this capability in as a > last-minute item and we haven't had a chance to update the code > internally to support the field. The infrastructure is already in place > to support it (ie all our geometry internally has methods to check on > getting the two-sided-lighting state), but we haven't done the field > handling. Shouldn't be that difficult to do, but we're in a > code-lockdown in preparation for the next milestone release. I'll have a > chat here with the guys to see if it's something we can fit in (even if > it is just to read the field and ignore for now)
Cool...that sounds great. > No, from the internals of our rendering system. Probably not much use to > you if you're using X3D/VRML directly, but if you're doing your own > coding for Java3D content, that's an example of how to do it. OK...I grabbed an older snapshot of the code (M5) and tracked it down... > > > I haven't been able to track down the current source on the site yet. > > As a rule, the dev releases do not zip up the source. That's because it > is typically just a cut of the code from one of our development machines > (usually mine). There's a lot of extra stuff there - stuff which doesn't > compile, or not in the formal compilation list for release etc. So to > get the current source, you need to grab it from CVS. Details are here: > > http://www.xj3d.org/cvs.html OK...I'll probably do that and try to implement it myself just so I can get going on my prototype. thanks for the help, kddubb =========================================================================== 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".
