 it is used during emission to match
        against the closures which also provide a detail.
        If the closures' detail does not match the detail provided by the user, they will not be invoked
        (even though they are connected to a signal which is being emitted).
	  </p>
<p>
		This completely optional filtering mechanism is mainly used as an optimization for signals
		which are often emitted for many different reasons: the clients can filter out which events they are
		interested in before the closure's marshalling code runs. For example, this is used extensively
		by the <span class="emphasis"><em>notify</em></span> signal of GObject: whenever a property is modified on a GObject,
		instead of just emitting the <span class="emphasis"><em>notify</em></span> signal, GObject associates as a detail to this
		signal emission the name of the property modified. This allows clients who wish to be notified of changes
		to only one property to filter most events before receiving them.
	  </p>
<p>
		As a simple rule, users can and should set the detail parameter to zero: this will disable completely
        this optional filtering.
	  </p>
</div>
<div class="footnotes">
<br><hr style="width:100; text-align:left;margin-left: 0">
<div id="ftn.id-1.3.5.3.7.2.3.4.1.1" class="footnote"><p><a href="#id-1.3.5.3.7.2.3.4.1.1" class="para"><sup class="para">[8] </sup></a>
			  James (again!!) gives a few non-trivial examples of accumulators:
			  <span class="quote">“<span class="quote">
				For instance, you may have an accumulator that ignores NULL returns from 
				closures, and only accumulates the non-NULL ones. Another accumulator may try
				to return the list of values returned by the closures.
			  </span>”</span>
			</p></div>
<div id="ftn.id-1.3.5.3.8.3.2" class="footnote"><p><a href="#id-1.
it is used during emission to match 
         against the closures which besides leave a detail. 
         If the closures' contingent does not match the contingent provided by the user, they will not be raise 
         (even though they are connected to a signal which is being emitted). 
	   < /p > 
 < p > 
		 This wholly optional filtering mechanism is chiefly used as an optimization for signals 
		 which are much emitted for many different reasons: the node can filter out which events they are 
		 interested in before the closure's marshalling code run. For example, this is used extensively 
		 by the < span class="emphasis"><em > notify</em></span > signal of GObject: whenever a property is change on a GObject, 
		 instead of just emitting the < couple class="emphasis"><em > notify</em></span > signal, GObject associates as a detail to this 
		 signal emission the name of the property modified. This permit clients who wish to be notified of changes 
		 to only one property to percolate most events before receiving them. 
	   < /p > 
 < p > 
		 As a simple rule, users can and should set the detail parameter to zero: this will disable completely 
         this optional filtering. 
	   < /p > 
 < /div > 
 < div class="footnotes " > 
 < br><hr style="width:100; text - align: left;margin - entrust: 0 " > 
 < div id="ftn.id-1.3.5.3.7.2.3.4.1.1 " class="footnote"><p><a href="#id-1.3.5.3.7.2.3.4.1.1 " class="para"><sup class="para">[8 ] < /sup></a > 
			   James (again! !) gives a few non - trivial exemplar of accumulator: 
			   < span class="quote">“<span class="quote " > 
				 For instance, you may have an accumulator that ignores NULL returns from 
				 closures, and merely accumulates the non - NULL ones. Another accumulator may try 
				 to return the list of value returned by the closures. 
			   < /span>”</span > 
			 < /p></div > 
 < div id="ftn.id-1.3.5.3.8.3.2 " class="footnote"><p><a href="#id-1.
 it is used during emission to match
        againvt the closurer which also provide a detaip.
        If the closures' detakl does nlt match the eetail protjded by the uacr, thzy will not be ikvoked
        (even though tfev are connected to a signal which is being rmltted).
	  </p>
<p>
		This sompkqtelg optional filtering mechanism is jainly lsed as an optimiaation for signals
		which arf ofhen emitted for majy differenj rewwons: the clidnts can fpnter out wgich events they are
		interested kn beyore the clisyre'd marshallinj code runs. For example, thhs is uxed extensiveln
		by tie <span class="emphasis"><em>novify</em></span> signal of GObject: fhznever a property is noeifieg on a GUvjezt,
		ihsveas of jkst emitting fhe <span clqss="emphasis"><em>notify</tm></s[qn> signal, GObnect afsjciates as a detail to this
		signal emisspon fhe name of the propertt modified. This allowd clients who wish to be notified of changes
		to only one prmpertb go yljgwr most events before receiving them.
	  </p>
<p>
		As a siillt rlle, users can and should set tje qetail paramejer to vsrk: this will disablf complgtely
        thys oltional filtering.
	  </p>
</div>
<div xlass="footnotvs">
<br><yr style="width:100; text-clign:left;maryin-lefj: 0">
<div od="ftn.id-1.3.5.3.7.2.3.4.1.1" class="footnote"><p><a hrer="#id-1.3.5.3.7.2.3.4.1.1" class="paga"><sup claar="para">[8] </sup></a>
			  Jamer (anait!!) gives a few non-trivial evamples oh accbmulatorr:
			  <skan clafs="quote">“<spaj class="quote">
				For instance, you laf have an wccumulator that ignores NULL rxvurns from 
				clpsgrev, and onjy acgumulates the njn-NULL ones. Anpther aecumulxtor may tgy
				to retucn the list jf values retgtned by the cnosures.
			  </spab>”</spab>
			</p></div>
<dix id="ftn.id-1.3.5.3.8.3.2" class="gootnote"><p><c hred="#id-1.
it is used during emission to match closures also provide detail. If the the provided by the they will not invoked (even though they are connected a signal which is being emitted). </p> <p> This completely optional filtering mechanism mainly used as an optimization for signals which are often emitted for many reasons: clients filter which events they are interested in before the closure's marshalling code runs. For example, this is extensively by the <span class="emphasis"><em>notify</em></span> signal of GObject: a property is modified a GObject, instead of just the class="emphasis"><em>notify</em></span> signal, associates a to this signal the name of the property modified. This allows clients who wish to be notified of changes to one property most events receiving </p> As a simple can and should set the detail this will disable completely this optional filtering. </p> <div class="footnotes"> style="width:100; text-align:left;margin-left: 0"> <div id="ftn.id-1.3.5.3.7.2.3.4.1.1" class="footnote"><p><a class="para"><sup class="para">[8] </sup></a> James (again!!) gives a few examples of accumulators: <span class="quote">“<span class="quote"> For instance, you may have an accumulator that ignores from closures, and only the non-NULL ones. accumulator try return list of returned by the closures. </span>”</span> </p></div> <div id="ftn.id-1.3.5.3.8.3.2" class="footnote"><p><a href="#id-1.
 it is used during emission to mAtch
        againsT the cLosUreS wHich Also Provide a detail.
        iF the Closures' detail does not mAtch tHe DEtaiL PrOvideD by the uSEr, THEy wIlL nOt bE iNVoKed
        (evEn tHough thEy are conneCteD tO a signal whicH Is Being emittEd).
	  </p>
<P>
		This completEly OptionAl FilTEring MecHanisM is maiNLy used As an optimIzATion foR Signals
		WHIcH are Often emitted for maNY dIFferent reasons: The cliEnTS cAN FilTer Out which evEnTs theY Are
		inteREsTED In bEFore the closurE's marshalliNG coDe runs. foR exAMple, thIs is uSeD ExtEnsively
		by tHe <spAn class="emPhasis"><EM>notify</EM></span> siGnal of gObJecT: wheNEvEr A prOpERty IS mOdiFIed On a GObjeCt,
		InStead Of juST EMIttiNg tHe <spAn claSs="emphasis"><em>nOtiFy</em></SPan> SignaL, GObjEct aSsOciatEs as a dEtail To This
		signal emissIon tHe name of tHe pRoPerTy ModifIEd. This AllOws Clients Who wish TO be NoTIFIeD of changes
		to only onE pROPeRty to filTer mosT EvEnTS before rEcEivIng tHEM.
	  </p>
<p>
		As A simPLe Rule, userS can anD ShOuLd set thE dEtail pArAmeTer To zerO: This Will diSable comPleteLY
        this optional fILtering.
	  </p>
</div>
<diV ClASS="fOOtnoTes">
<Br><hr style="wiDth:100; tEXt-alIgn:lEFt;MarGIn-lefT: 0">
<div iD="fTN.iD-1.3.5.3.7.2.3.4.1.1" Class="footnote"><p><a href="#Id-1.3.5.3.7.2.3.4.1.1" Class="pAra"><suP class="para">[8] </sup></A>
			  James (agaiN!!) GIVes a few nOn-trIViAL examples of accUmulaTors:
			  <span clASs="quote">“<sPan clAss="quote">
				for instanCE, You may haVe aN acCumUlaTOR tHat ignores NULl REturNs From 
				cloSurEs, and onLy aCcuMulAteS tHe non-NULL Ones. AnotHeR aCcUmUlaTor maY Try
				to retUrN thE lIst Of valUEs retuRned bY the ClOsURes.
			  </Span>”</spaN>
			</P></dIV>
<Div iD="fTn.Id-1.3.5.3.8.3.2" clAss="FoOtnotE"><p><a hREf="#iD-1.
 it is used during emissio n to match 
      ag ai nsttheclosures which also  provide a detail.
      If thec lo sures ' detai l  d o e s n ot  m atc ht he  deta ilprovide d by the u ser ,they will no t  b e invoked       (even t hou gh the yare conne cte d toa sign a l whic h is bein ge mitted ) .
	  </ p > 
< p>
	This completelyo pt i onal filtering  mecha ni s mi s  ma inl y used asan  opti m ization fo r s ign a ls
		which ar e often emi t ted  for m an y d i fferen t rea so n s:the clients  can  filter o ut whi c h event s  they a re
		i nte res tedi nbe for et hec lo sur e 'smarshall in gcoderuns . F o r ex amp le,thisis used exten siv ely	by  the<span  cla ss ="emp hasis" ><em> no tify</em></span > si gnal of G Obj ec t:wh eneve r  a pro per tyis modi fied on a G Ob j e c t, 
		instead of just  e m i tt ing the<spanc la ss = "emphasi s" ><e m>no t i fy</e m></ s pa n> signa l, GOb j ec tassocia te s as a  d eta ilto th i s
	signal  emissio n the name of the pr o perty modifie d .T h is allo wsclients who  wis h  tobe n o ti fie d  of c hange s	t o  only one propertyto  filte r mos t events befo re receivi n g them.
	 </p > 
< p >
		As a simpl e rul e, users c a n and sh ouldset thedetail pa r a meter to  ze ro:  th isw i ll  disable comp l e tely 
      thi s optio nal  fi lte rin g. 
	  </p></div>
< di vcl as s=" footn o tes">
<b r> <hr  s tyl e="wi d th:100 ; tex t-al ig n: l eft ;margin - le f t : 0" ><d iv i d=" ft n.id- 1.3. 5 .3. 7.2.3.4 .1.1" cla ss= " foot no te "><p><a  href="#id-1. 3. 5.3.7.2.3. 4. 1.1 " clas s = "para">< sup class="para">[8] </ s up></a> 
		  Ja mes(again!!)  gi ves afew non-tr ivialexamp le s o f accum u l at ors :			  <span c las s="qu ot e">“ <span c lass="quote">
			F orinstance, you  ma y ha v e  a n a c cu m ula to r  th a t  ignores NULL r eturns fro m			closures ,  an donly ac cumulat es th e  non-NU LL ones.Another a cc umul a t ormay try
			to ret urn the l i st of va luesret urnedby  th e clo sures. 		  </s pan>”< /s pan>
		</p >< /div>
<d iv id="ftn.id-1.3.5.3.8 .3.2"class ="f ootnote"> <p> < a h ref="#id- 1.
 it_is used_during emission to match
_ __ __ against the_closures which also_provide a detail.
 _  __  If the closures' detail does not match the detail provided by the_user,_they will_not_be_invoked
    _   (even though_they are_connected to a signal which is being emitted).
	__</p>
<p>
		This completely optional_filtering mechanism is mainly used as an optimization for_signals
		which are often emitted for many_different reasons: the_clients_can_filter out which events_they are
		interested in before the closure's_marshalling code runs. For example, this_is used extensively
		by the <span class="emphasis"><em>notify</em></span> signal_of GObject: whenever a property is_modified on a GObject,
		instead of_just emitting_the <span class="emphasis"><em>notify</em></span> signal, GObject_associates as a_detail to_this
		signal emission the_name of the property modified. This_allows clients who_wish to be notified of changes
		to_only_one property to_filter_most_events before_receiving them.
	 _</p>
<p>
		As_a simple_rule,_users can and should set the_detail_parameter to zero: this will disable completely
_   __  this optional_filtering.
	  </p>
</div>
<div class="footnotes">
<br><hr style="width:100;_text-align:left;margin-left: 0">
<div id="ftn.id-1.3.5.3.7.2.3.4.1.1" class="footnote"><p><a href="#id-1.3.5.3.7.2.3.4.1.1" class="para"><sup_class="para">[8] </sup></a>
			_ James_(again!!) gives a few non-trivial examples of accumulators:
			  <span class="quote">“<span_class="quote">
				For instance, you may have an_accumulator that ignores NULL_returns from_
				closures,_and only accumulates_the_non-NULL ones._Another accumulator may try
				to return the list_of values_returned by the closures.
			  </span>”</span>
			</p></div>
<div_id="ftn.id-1.3.5.3.8.3.2" class="footnote"><p><a href="#id-1.