Hi Arturo,
please try to cache the content of the event in a local variable. This
may help: var data = e.getData() and use this variable inside your
interval callback.
Sebastian
a.jimenez schrieb:
> Hello all,
>
> I am using version 0.6.6 (sorry, too tight schedule to update to 0.7), and I
> am having a problem with timers and events. The problem is that I have an
> intensive process and I have to show an hourglass in the meantime. I saw in
> previous posts a solution by Sebastian that implies to use a Timer. My code
> is as follows:
>
> qx.Proto._onChangeCombo = function(e) {
> var intensiveFunction = function(__e) {
> ...
> };
> qx.ui.core.ClientDocument.getInstance().setGlobalCursor("wait");
> var vTimer = new qx.client.Timer(0);
> this.debug(e.getData()); // works fine
> vTimer.addEventListener("interval", function(e1) {
> this.debug(e.getData()); // shows null; why? timer event is e1!!!
> intensiveFunction.call(this, e);
> vTimer.dispose();
> qx.ui.core.ClientDocument.getInstance().setGlobalCursor("default");
> }, this);
> vTimer.start();
> };
>
> My problem is that the first debug shows me the right ListItem object (the
> main event type is changeSelected), but the inner debug message shows me
> null. I cannot understand why. Please help me!
>
> Thanks,
> -arturo
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
