Can't agree more. :-)
Michael Pfeiffer wrote:
Exactly. Every thing else sounds like a program design problem. This
queue
also would allow it to send all data to the (fictious?) other receiver of
the data and only the necessary amount to J3D.
===
Chien,
Thanks for the explanation what happens. I change the transformation
inside a mouseDragged method. So, about 16 TransformGroups (in my test
case) are called on each mouse movement. This can't be handled so fast
inside Java3D and the queue is growing (I suppose, the whole Transform3D
object
We have released a new version, 445, of "Jun for Java".
The major changes since the version 441 includes:
* JunGaugeModel is a class for specifying a value with a
gauge by a mouse or arrow keys, and JunGaugeDialog shows a
dialog to request a value with JunGaugeModel.
ht
