Hi Martijn,
I would use it if you don't want bubbling! ;)
In this special case I can't tell you why back then (4-5 years ago) this
was preferred. I can only think of general advantages:
- I would expect a slightly performance gain
- you are also preventing that the DOM Node parent chain upwards reacts
on that event which you may not want (if you are using this event
frequently in your application)
Regards
Richard
Am 17.01.13 17:30, schrieb Martijn Verbrugh:
> Hi,
>
> In what cases should one use fireNonBubblingEvent() instead of
> fireEvent()? I saw it used in the qx.ui.window.Window class:
>
> close : function()
> {
> if (!this.isVisible()) {
> return;
> }
> if (this.fireNonBubblingEvent("beforeClose", qx.event.type.Event,
> [false, true]))
> {
> this.hide();
> this.fireEvent("close");
> }
> },
>
> But I do not really understand why a /non bubbling/ event is preferred here.
>
> Thanx.
>
> Regards,
>
> Martijn.
>
------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
