🚀 go-pugleaf

On Mon, 08 Nov 1999 09:50:19 +0000, Steve Horsley wrote:

> I have never bothered to check if I am on the event thread
> before using invokeLater. In everything I have written
> invokeLater in, it has always been pretty obvious that I
> will not be on the event thread anyway. In the example
> above, the counter changes were always caused by the
> transmit timer thread (transmit packet count) or the
> socket listener thread (rx packet count). I think that 
> performing this check is more likely to waste time than
> save it.

In my case, most of the events will occur entirely on the event thread, 
in direct response to the user dragging things around the screen, 
resizing objects, etc.  This is where the response is the most critical.  
In the few threaded operations, the immediate response is less critical, 
since it will be part of a rather lengthy operation.  

So the test will eliminate operations when they count, and only cost more 
when it does not.  My guess is that it will help in this case, although I 
doubt that it will be clearly perceivable.  But it will just be a single 
line of code, so I think I will try it.

-- 
John P. McGrath
<mcgrath@enter.net>
<jpm@nscs.fast.net>