Hi Stefan,
Yes, your event handler was a perfect solution:
this.addListenerOnce("appear", function() {
this.center();
}, this);
Now my next task will be to login the user before he/she can open new
windows. I'm a bit stuck, because I do not see anything that looks like the
"main event loop" found in other windowing toolkits.
I know how to set the login window to modal, e.g. "this.setModal(true)". But
this is not a "function call" that returns. I cannot "suspend" the call
chain from my main application, until the user closes the login window. In
other toolkits like wx, I would be able to call ShowModal() and get the
return value in the next line of code. Something like:
dlg = create_modal_dialog();
dlg.ShowModal(); # Here the main app's execution is suspended until the
modal window is closed
login_information = dlg.GetLoginInfo();
destroy(dlg)
....
In qooxdoo, I only see one way to do it: let the login window call back
another method (or event handler) in the main application. But I do not like
the idea because I'll be using hundreds of modal windows. Maybe I missed
something.
Thanks
Laszlo
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/bounds-is-null-SOMTIMES-tp5780325p5781247.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
