Description
Greg, hello;
in this thread:
http://mail-archives.apache.org/mod_mbox/pivot-user/201001.mbox/%3C4B5E581D.2080604@hms.harvard.edu%3E
your final word is:
"Sorry, it is not possible"
but I know that you know that it is possible
the reason I need this is same as Martin here:
http://netbeans.org/bugzilla/show_bug.cgi?id=90590
namely: do some cleanup after shutdown was requested and confirmed:
org.apache.pivot.wtk.Application
public boolean shutdown(boolean optional) throws Exception;
since you call shutdown(boolean optional) from EDT I need to block it, using this approach:
http://bugs.sun.com/view_bug.do?bug_id=6424157
wich "almost works", except you have this check everywhere:
Container.assertEventDispatchThread();
which fails, as described above:
http://bugs.sun.com/view_bug.do?bug_id=6424157
due to EventQueue.isDispatchThread() failing on the "T1 vs T1*" distinction
my request is this:
do you think you could make
Container.assertEventDispatchThread();
less pedantic, and allow both "current and past/next" EDT threads to pass which are created during EventQueue push() / pop()
thanks!
Andrei
Attachments
Attachments
Issue Links
- relates to
-
PIVOT-780 Can't use BXMLSerializer from non-AWT threads makes background resource loading impossible
- Resolved