After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 751837 - Window "destroy" is not fired when SwingSet2 is closed.
Window "destroy" is not fired when SwingSet2 is closed.
Status: RESOLVED FIXED
Product: java-atk-wrapper
Classification: Applications
Component: general
0.33.x
Other All
: Normal normal
: ---
Assigned To: Magdalen Berns (irc magpie)
java-atk-wrapper maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-07-02 13:50 UTC by Magdalen Berns (irc magpie)
Modified: 2015-07-02 14:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Patch to fix destroy window events (1.14 KB, patch)
2015-07-02 14:16 UTC, Magdalen Berns (irc magpie) 		committed Details | Review

Description Magdalen Berns (irc magpie) 2015-07-02 13:50:17 UTC 
1. Run the python window listener script in a terminal.[1]
2. Run SwingSet2 with "java -jar SwingSet2.jar"
3. Close SwingSet2 by clicking on the cross at the top left of the app

The "create", "activate" and "deactivate" signals fire as expected but when closing the SwingSet2 application, "destroy" is not fired.
Comment 1 Magdalen Berns (irc magpie) 2015-07-02 14:16:21 UTC 
Created attachment 306623 [details] [review]
Patch to fix destroy window events

This seems to work. It seems that perhaps when the window is closed it's too late to get information from the TopLevel query so this has to be done whilst the window is closing instead. I haven't removed the call from windowClosing just to be on the safe side but I'll keep an eye on it and may remove it later.