On Tue, Feb 23, 2010 at 09:58, Fritz Zaucker <[email protected]>wrote:
> Hi,
>
> I am trying to send an rpc async call from within a drop event handler.
>
> The drop event handler works just fine (using debug console messages to
> verify) as long as I don't make an rpc call. With the rpc call I get
>
> Too much recursion:
>
> return qx.Bootstrap.getClass(value) == "Function"; Bootstrap.js
> (line 609)
>
> Even deferring the async call with qx.event.Timer doesn't work.
>
> Is this to be expected? If not, I'll try to get a small example together.
>
The possible issue I see is that when you're in an event handler, when you
return from that handler, the event (and all of its data) goes away. If
you're trying to do something that involves the need for that event to stick
around, that could cause problems. In principle, though, what you're trying
should be possible. We do RPC calls from button "execute" event handlers all
the time, so I'd expect it to work with drop events as well.
Derrell
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
