Hi Blair, thanks for your hints. I'm using a 3D - mouse and got no problems so far. But my COM port is running at 9600 Baud only. Maybe the blocking is a Java3D problem on winNT. We encountered that while running an animation the app doesn't accept any events (Java3D in combination with swing) and the desktop "hangs" . Also a Java3D app takes much more cpu time than under win95. Gernot [EMAIL PROTECTED] http://www.janet.de > -----Original Message----- > From: Blair MacIntyre [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 04, 1999 4:02 AM > To: [EMAIL PROTECTED] > Subject: [JAVA3D] CommAPI for writing InputDevices > > > In case anyone else out there is thinking of writing an input > device for > Java3D, using the CommAPI, I thought I'd pass on this little > experience. > > It appears that (at least on WindowsNT) there is a small bug, where > reads from the InputStream returned by a SerialPort device will > sometimes block for min(200ms, TimeOut) (where TimeOut is the timeout > value you set for your input stream). > > The workaround is to set your timeout value nice and low -- since I'm > reading from a tracker that is streaming data at 119200 baud, I set it > to 1ms timeout, and things seem to be quite happy. > > ============================================================== > ============= > 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".
