My web site - VirtualUniverse.mc.doWork(); Thread.yield(); } while(!VirtualUniverse.mc.mcThreadDone()); } } The constructor
VirtualUniverse.mc.doWork(); Thread.yield(); } while(!VirtualUniverse.mc.mcThreadDone()); } } The constructor for the MasterControlclass loads the J3D.DLL native DLL and reads the Java 3D system properties (see table 18.4). Message processing and threading architecture The MasterControlclass is a message exchange mechanism between the various subsystems that compose the Java 3D runtime. The MasterControlthread maintains five UnorderListmembers, each containing Java 3D worker threads. stateWorkThreads: RenderingAttributesStructurecalls updateMirrorObjecton the NodeComponentRetainedpassed with the message. GeometryStructuremaintains a binary hash tree of GeometryAtomobjects and Groups. Maintains the wakeupOnCollisionEntry, Exit, and Movementlists. BehaviorStructuremaintains a list of behaviors and marks them for activation. RenderingEnvironmentStructuremaintains a list of the lights, fog, alternate appearances, clipping regions, and backgrounds to be used for each RenderAtom. SoundStructuremaintains a list of sounds and soundscapes and schedules them for activation with the View s SoundScheduler. BehaviorScheduler, for all VirtualUniverseinstances, maintains a list of BillBoardbehaviors and behaviors in the system and calls the processStimulusmethod on each if marked for activation. Inputdeviceschedulermaintains lists of nonblocking and blocking input devices and calls the pollAndProcessInputmethod on the nonblocking devices. A new thread is created to handle the input from each blocking InputDevice. RenderBin, for each View, maintains lists of RenderAtomsthat describe rendering operations to be performed. The RenderBinimplements methods such as renderOpaque, renderBackground, renderOrdered, and renderTransparent, which are called by the Renderclass. SoundScheduler, for each View, maintains a list of SoundSchedulerAtomsand marks each for activation. The rendermethod iterates the scheduled SoundSchedulerAtomsand calls the startmethod on each. renderWorkThreads: Rendererfor each Canvas3D s Screen3D. The Renderclass runs the main Java 3D rendering loop by calling methods on the Canvas3Dclass and processing the RenderBinfor the Canvas3D s View. requestRenderWorkThreads: Rendererfor each Screen3Din the device render map. renderThreadData: Rendererfor each Screen3Dfor each View, including offscreen Renderers. inputDeviceThreads: A single Inputdevicescheduler. 316
We recommend high quality webhost to host and run your jsp application: christian web host services.