Updated docstrings generated documentation.

1 files changed, 35 insertions, 24 deletions

diff --git a/docstrings/pyinotify._ProcessEvent-class.html b/docstrings/pyinotify._ProcessEvent-class.html
index 8215277..7f9df62 100644
--- a/docstrings/pyinotify._ProcessEvent-class.html
+++ b/docstrings/pyinotify._ProcessEvent-class.html
@@ -55,21 +55,32 @@
   </tr>
 </table>
 <!-- ==================== CLASS DESCRIPTION ==================== -->
-<h1 class="epydoc">Class _ProcessEvent</h1><span class="codelink"><a href="pyinotify-pysrc.html#_ProcessEvent">source&nbsp;code</a></span><br /><br />
+<h1 class="epydoc">Class _ProcessEvent</h1><p class="nomargin-top"><span class="codelink"><a href="pyinotify-pysrc.html#_ProcessEvent">source&nbsp;code</a></span></p>
 <center>
-<center>  <map id="uml_class_diagram_for_pyinotif_22" name="uml_class_diagram_for_pyinotif_22">
-<area shape="rect" href="pyinotify.ProcessEvent&#45;class.html" title="Process events objects, can be specialized via subclassing, thus its behavior can be overriden:" alt="" coords="45,104,139,130"/>
-<area shape="rect" href="pyinotify.ChainIf&#45;class.html" title="Makes conditional chaining depending on the result of the nested processing instance." alt="" coords="16,160,69,186"/>
-<area shape="rect" href="pyinotify.Stats&#45;class.html" title="pyinotify.Stats" alt="" coords="120,160,165,186"/>
-<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html#__repr__" title="repr(x)" alt="" coords="111,36,231,54"/>
-<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html#__call__" title="To behave like a functor the object must be callable." alt="" coords="111,54,231,73"/>
-<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html" title="Abstract processing event class." alt="" coords="109,10,232,74"/>
-<area shape="rect" href="pyinotify._SysProcessEvent&#45;class.html" title="There is three kind of processing according to each event:" alt="" coords="189,104,312,130"/>
+  <div class="private"><center>  <map id="uml_class_diagram_for_pyinotif_26" name="uml_class_diagram_for_pyinotif_26">
+<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html#__call__" title="To behave like a functor the object must be callable." alt="" coords="108,36,228,54"/>
+<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html#__repr__" title="repr(x)" alt="" coords="108,54,228,73"/>
+<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html" title="Abstract processing event class." alt="" coords="107,10,229,74"/>
+<area shape="rect" href="pyinotify.ProcessEvent&#45;class.html" title="Process events objects, can be specialized via subclassing, thus its behavior can be overriden:" alt="" coords="41,104,135,130"/>
+<area shape="rect" href="pyinotify._SysProcessEvent&#45;class.html" title="There is three kind of processing according to each event:" alt="" coords="185,104,311,130"/>
+<area shape="rect" href="pyinotify.Stats&#45;class.html" title="pyinotify.Stats" alt="" coords="16,160,61,186"/>
+<area shape="rect" href="pyinotify.ChainIf&#45;class.html" title="Makes conditional chaining depending on the result of the nested processing instance." alt="" coords="112,160,165,186"/>
 </map>
-  <img src="uml_class_diagram_for_pyinotif_22.gif" alt='' usemap="#uml_class_diagram_for_pyinotif_22" ismap="ismap" class="graph-without-title" />
-</center></center>
+  <img src="uml_class_diagram_for_pyinotif_26.gif" alt='' usemap="#uml_class_diagram_for_pyinotif_26" ismap="ismap" class="graph-without-title" />
+</center></div>
+  <div class="public" style="display:none"><center>  <map id="uml_class_diagram_for_pyinotif_27" name="uml_class_diagram_for_pyinotif_27">
+<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html#__call__" title="To behave like a functor the object must be callable." alt="" coords="28,36,148,54"/>
+<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html#__repr__" title="repr(x)" alt="" coords="28,54,148,73"/>
+<area shape="rect" href="pyinotify._ProcessEvent&#45;class.html" title="Abstract processing event class." alt="" coords="27,10,149,74"/>
+<area shape="rect" href="pyinotify.ProcessEvent&#45;class.html" title="Process events objects, can be specialized via subclassing, thus its behavior can be overriden:" alt="" coords="41,104,135,130"/>
+<area shape="rect" href="pyinotify.Stats&#45;class.html" title="pyinotify.Stats" alt="" coords="16,160,61,186"/>
+<area shape="rect" href="pyinotify.ChainIf&#45;class.html" title="Makes conditional chaining depending on the result of the nested processing instance." alt="" coords="112,160,165,186"/>
+</map>
+  <img src="uml_class_diagram_for_pyinotif_27.gif" alt='' usemap="#uml_class_diagram_for_pyinotif_27" ismap="ismap" class="graph-without-title" />
+</center></div>
+</center>
 <hr />
-Abstract processing event class.<br /><br />
+<p>Abstract processing event class.</p>
 
 <!-- ==================== INSTANCE METHODS ==================== -->
 <a name="section-InstanceMethods"></a>
@@ -196,10 +207,10 @@ Abstract processing event class.<br /><br />
   </td><td align="right" valign="top"
     ><span class="codelink"><a href="pyinotify-pysrc.html#_ProcessEvent.__call__">source&nbsp;code</a></span>&nbsp;
     </td>
-  </table>
+  </tr></table>
   
-  To behave like a functor the object must be callable. This method is a
-  dispatch method. Lookup order:
+  <p>To behave like a functor the object must be callable. This method is a
+  dispatch method. Lookup order:</p>
   <ol start="1">
     <li>
       process_MASKNAME method
@@ -224,8 +235,8 @@ Abstract processing event class.<br /><br />
               executing next chained functors (see chain.py example).
             </li>
             <li>
-              Returning True instead means do not execute next 
-              processing functions.
+              Returning True instead means do not execute next processing 
+              functions.
             </li>
           </ul></dd>
     <dt>Raises:</dt>
@@ -248,12 +259,12 @@ Abstract processing event class.<br /><br />
   </td><td align="right" valign="top"
     ><span class="codelink"><a href="pyinotify-pysrc.html#_ProcessEvent.__repr__">source&nbsp;code</a></span>&nbsp;
     </td>
-  </table>
+  </tr></table>
   
-  repr(x)
+  <p>repr(x)</p>
   <dl class="fields">
     <dt>Overrides:
-      object.__repr__
+        object.__repr__
         <dd><em class="note">(inherited documentation)</em></dd>
     </dt>
   </dl>
@@ -286,10 +297,11 @@ Abstract processing event class.<br /><br />
 <table border="0" cellpadding="0" cellspacing="0" width="100%%">
   <tr>
     <td align="left" class="footer">
-    Generated by Epydoc 3.0beta1 on Sun Aug 10 13:37:39 2008
+    Generated by Epydoc 3.0.1 on Tue Jan  6 22:57:24 2009
     </td>
     <td align="right" class="footer">
-      <a href="http://epydoc.sourceforge.net">http://epydoc.sourceforge.net</a>
+      <a target="mainFrame" href="http://epydoc.sourceforge.net"
+        >http://epydoc.sourceforge.net</a>
     </td>
   </tr>
 </table>
@@ -300,9 +312,8 @@ Abstract processing event class.<br /><br />
   // javascript is turned off then we want them to be
   // visible); but by default, we want to hide them.  So hide
   // them unless we have a cookie that says to show them.
-  checkCookie()
+  checkCookie();
   // -->
 </script>
-  
 </body>
 </html>