Justin Couch wrote:
> For example
> - tell me how WakeupOnSensorEntry works?
I think that Sensor class javadoc is quite enough to make sense out of
it.
Example of usage of WakeupOnSensorEntry class would be (my example after
reading docs for one minute) creating touch-and-expand menu (Johny
Mnemonic style) for virtual glove. View (head) would be in same place,
but hand (Sensor) would enter menu bounds and behaviour would fire up
(expanding menu with a lot of fx).
This is first time I've looked at Sensor/WakeupOnSensorEntry class. If
I'm right, then I think that docs are all right to person who never
touched a virtual glove and only by reading this very doc discovered
that hand position in this case has to be separate from view position.
As for the clockwise rule - yes I also agree it should be stressed very
clearly. But I don't think it should be mentioned in first chapter -
bold font note inside chapter about GeometryArrays and another one near
the PolygonAttributes CULL_* would be enough :) After all most people
are going to use externally created models anyway - and transforms,
branchgroups and appearances are a lot more important for them then raw
polygon creation rules.
I have nothing against good documention. I just do not think that
focusing at docs at cost of other things is a good idea - especially
given stability problems. Person can ask for help on net if he does not
understand a docs, but is helpless when app crashes on client machine.
Artur
===========================================================================
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".
