Thomas, It looks like you DO see want I want :) I knew that the qooxdoo bubbling kind of went up and down the bubble chain, but I didn't know if I was going to be able to get at it before it got to the window itself. Apparently not.
I may have to subclass the window manager and modify the default behaviour, but it will have to wait a while before I can get around to figuring out the best way to do it. That goes for the enhancement bug that you mentioned. I didn't even know there was such a thing! My windows are not really 'popup-windows'. It is just that they have a kind of (very loose) parent/child relationship with the main window. I think that there needs to be a way to specifiy relationships between windows. I think that this type of behaviour is going to be very important as applications get more sophisticated. But it needs alot of thought put into it. tom thron7-2 wrote: > > > 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. > > Yes, I would look into the window manager. Maybe you can subclass it and > implement a different behaviour. > > 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 > > -- View this message in context: http://www.nabble.com/Keep-window-from-getting-click-event-tp22963986p23048985.html Sent from the qooxdoo-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
