Overriding bind and unbind"
From Documentation
Tmillsclare (talk | contribs) m |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
[[File:ZKComDevEss_bind_.png]] | [[File:ZKComDevEss_bind_.png]] | ||
| − | The <javadoc directory="jsdoc" method="unbind_(zk.Skipper, _global_.Array)" class="false">zk.Widget</javadoc> function is very similar. Upon detaching | + | The <javadoc directory="jsdoc" method="unbind_(zk.Skipper, _global_.Array)" class="false">zk.Widget</javadoc> function is very similar. Upon detaching the widget from the DOM the <javadoc directory="jsdoc" method="unbind_(zk.Skipper, _global_.Array)" class="false">zk.Widget</javadoc> method is called to enable us to perform tasks such as adding and removing listeners to avoid memory leaks. The diagram below demonstrates this. |
[[File:ZKComDevEss_unbind_.png]] | [[File:ZKComDevEss_unbind_.png]] | ||
Latest revision as of 04:38, 11 August 2011
The following diagrams outline when the bind_(Desktop, Skipper, Array) and unbind_(Skipper, Array) methods are called. Firstly let’s take a look at how binding works.
The unbind_(Skipper, Array) function is very similar. Upon detaching the widget from the DOM the unbind_(Skipper, Array) method is called to enable us to perform tasks such as adding and removing listeners to avoid memory leaks. The diagram below demonstrates this.
Now that we have had a brief introduction of bind_(Desktop, Skipper, Array) and unbind_(Skipper, Array) let’s see the methods put into action when we bind appropriate listeners for events.