Raj, I like to use Java threads whenever my program will seem unresponsive to the user, such as the situation you describe below. It is polite to leave your user interface in an appropriate state. You can set the thread priority to make sure that your calculation gets significant CPU resources, and a modal dialog will let the user know that the program is calculating and also prevent them from tying up the CPU by interacting with Swing. You may even consider adding a progress bar to monitor the progress of your calculation.
Good luck, Todd Raj Vaidya wrote: >To All Ye Thread Gurus: > >Is fiddling with threads worth the trouble in a Java3D App.? > >For example, at the click of a Swing button my app. does >very highly numerically intensive computations to create >a geometry and subsequently makes it *live*. At the time >when the geometry is being created, I would like all >CPU resources to be dedicated to just that and minimally, >if at all, to anything else. Would the resources allocated >to the various threads(?) ( viz. Swing thread, the Java3D >renderer thread, behavior threads etc) grossly affect that >allocated to numerical computations (FLOPS). If so, are there >safe/adventurous ways of handling the problem with/without >regard to portability ? > >Any ideas welcome !!! > >Happy New Year Everybody > >Raj Vaidya > >=========================================================================== >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". > =========================================================================== 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".
