Ted Neward wrote:
> Because Swing is a fully lightweight library, it can't rely on any of the
> operating-system-specific constructs underneath the JVM to more efficiently
> make use of the CPU. Instead, it spins off a daemon thread to (basically)
> poll the OS for the mouse position and information and broadcast that
> information to the Swing JComponents under the mouse pointer at that
> moment.
This sounds suspicious. Is this conjecture or based on analyzing the Swing code?
There's always an AWT window under a top-level Swing window, and I would expect
Swing to be using AWT events to be tracking input devices.
Not that there aren't a lot of CPU-sucking details buried in Swing (or
lightweight components in general)... I just question whether this is one of
them.
Nathan
---------------------------------------------
This message was sent using Endymion MailMan.
http://www.endymion.com/products/mailman/
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
