I am reading your stack trace but I defintely never mentioned the
double invocation to handle that I see there are evidencing anything.
The issue is the value of debugCounter at a two certain moments in the
application - in the two calls to showDebugInformation.
Although the proof that I am
I did not say it was another Thread. In fact, I said it was the Java
Application Thread itself- being recursively re-entrant.
Specifically, at the time the MOUSE_EXITED_TARGET event is generated,
the Java Application Thread has a choice- continue proocessing the
EventHandler#handle method
I see nothing special in the stack trace.
When you remove the component, a new MouseEvent *must* trigger
(MouseEvent.EXITED) as it always needs to match with MouseEvent.ENTERED.
So, the call to 'remove' triggers a new event, which gets handled by the
same handler. It is indeed entered
Hi All,
I spent some time refactoring the program which displays this bug. It's
now small enough to share the source in an email, but it is very very
dense and the proof of bug, one specific line to standard I/O,
requires the source code to be read and understood in order to see the
bug. As