panyasan wrote:
>
> Looking through the code, my assumption is that it has to do with
> qx.event.Registration.getManager(). The event manager is chosen according
> to the global "window" object (line 78). This is really tricky, because
> the event target is instantiated in the parent window, and not in the
> child window. I wonder if an additional argument could be added to
> addListener(), i.e. "addListener("type",handler,this,window), so that the
> correct window context could be figured out by the getManager() method
>
>
I tried to patch the code to retrieve the window of the event target object
from getContainerElement().getDomElement(), but I guess that would have been
too easy. ;-) The result was that clicking on the Button no longer worked
(before it did, but the "execute" event was not fired). I guess random
hacking without understanding the internals doesn't make much sense here.
There is a bug for that in bugzilla already. I would be thrilled if the core
team would find the issue interesting enough to invest some development
time. I am happy to work on this if I get some clues as to what would need
to be changed.
Thanks,
Christian
--
View this message in context:
http://n2.nabble.com/Native-Window-again-tp3723200p3755408.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
