> I was really hoping that I could keep the click event on the button from
> reaching the window underneath it.

I'm not sure this is actually what you want. The button is a child of the
window widget, and qooxdoo implements capture-then-bubble event phases.
That means the Window object has to get the event first, before it reaches
the Button. At the Button, you could install an event handler that
prevents the bubbling phase by stopping the propagation, but my gut
feeling is this is attacking the problem from the wrong side. The Window
object *has* to get the event, at least once.

But you don't want to constraint the event phases. You want the Window to
stay in the background.

> I have looked at the
> qx.ui.window.Window
> (and related window files) source files briefly, but didn't see anything
> obvious that I could do.  I assume that the qx window manager uses the
> window Zindex property and it seems like messing with the zindex  might
> conflict with the window managers job.  (though, I might have to do
> exactly
> what you suggested!)

Yes, I would look into the window manager. Maybe you can subclass it and
implement a different behaviour.

>  My problem is not a show stopper, and I will look at
> the code more closely when I get time to try to find a solution.  I am not
> ungrateful for your suggestion, but it seems that there ought to be a
> better
> way.

If I got you right, what you actually want is a kind of "always-on-top"
for your pop-up windows, the kind of attribute you can set in some desktop
environments, right?! The primary window and its buttons should process
events as usual, but the window manager should keep the pop-ups in the
forground. I think this makes sense, but as far as I can tell the default
window manager doesn't offer this. Maybe its worth to open an enhancement
bug for this.

Thomas


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to