I posted comments on the previously referenced post. There's a suggestion to
delay the destruction of the window via a one-shot timer such that current
processing can be completed. This method seems to solve my problems. Here
is an example of it's usage:
var win = new
dohickie.ui.configuration.ConfigurationWindow(this.__mdvr.getConfiguration());
win.setModal(true);
win.addListener("myWhizBangEvent", this._handleWhizBang, this);
function cleanUp() {
// Setup a timer routine to call immediately. Using a timer routine
// will guarantee that the current thread of processing will complete
// before this function is called.
qx.util.TimerManager.getInstance().start(
function() {
win.destroy();
win = null;
}
);
}
win.addListener("close", cleanUp, win);
win.open();
-----
"The wise know their weakness too well to assume infallibility; and he who
knows most, knows best how little he knows." - Thomas Jefferson
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Programmatically-closing-Window-while-contained-tooltip-open-causes-problems-tp6518756p6527559.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
