Oleg Sukhodolsky wrote:
On Mon, Feb 16, 2009 at 1:51 PM, Roman Kennke <[email protected]> wrote:
Hiyo,
as far as I can see hideAndDisposeHandler() called either from hide()
(if it is not called by dispose()) or
from doDispose(), but after super.doDispose() is executed.
You are right. My original analysis was not correct. The problem is a
little
diferent, the application I have here calls hide() and dispose() one
after
the other, which then causes this situation, hideAndDisposeHandler()
called
first, followed quickly by Window.doDispose(). The attached test program
demonstrates the problem. Not executing the DisposeAction immediately,
but
instead sending it over the EQ solves the problem by bringing the actions
into correct order. This would be a good case for testing the brand new
bugzilla, no? ;-)
Yes, I agree with you. Now you have good bugreport (and good bug to
report ;) to test
new system :)
Hrmpf. Seems I cannot. The disclaimer says 'During the initial rollout
phase, this site will only be accepting and tracking patch contributions
from developers without push access to the OpenJDK 6 and 7 forests.' and
since I _have_ push access, I can't file bug reports. Too bad.
BTW, simply sending this over the EQ is no solution either, because then
later it will fail to invokeAndWait(). I will think a little more about
this, or maybe anybody has a quick idea?
Just an idea (have not evaluated it carefully):
perhaps we should set keepBlockingEDT to false not in hideAndDisposeHandler(),
but in WakingRunnable.run() instead.
I'm looking at this problem at the moment. The problem is the instance
of WakingRunnable is not run on EDT at all - I don't know why.
Thanks,
Artem
Oleg.
/Roman
--
Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org
aicas Allerton Interworks Computer Automated Systems GmbH
Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
http://www.aicas.com * Tel: +49-721-663 968-48
USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe
Geschäftsführer: Dr. James J. Hunt
