diff engine/extensions/pychan/events.py @ 251:92c7ce181881

Documentation cross reference fixes.
author phoku@33b003aa-7bff-0310-803a-e67f0ece8222
date Fri, 27 Mar 2009 11:52:55 +0000
parents e4dfdf4c11fd
children 51cc05d862f2
line wrap: on
line diff
--- a/engine/extensions/pychan/events.py	Thu Mar 26 17:13:03 2009 +0000
+++ b/engine/extensions/pychan/events.py	Fri Mar 27 11:52:55 2009 +0000
@@ -1,16 +1,15 @@
 # -*- coding: utf-8 -*-
-#coding: utf-8
 
-"""
-PyChan event handling
-=====================
+"""\
+PyChan event handling (internal).
+=================================
 
 Users shouldn't need to use this module directly.
 L{widgets.Widget.capture} and L{widgets.Widget.mapEvents} provide
 a convenient API to capture events.
 
 Nevertheless to understand how its supposed to work
-take a look at L{EventMapper} and L{EventListener}
+take a look at L{EventMapper} and L{EventListenerBase}
 
 Event callbacks
 ---------------
@@ -40,6 +39,7 @@
 """
 
 from compat import guichan
+import widgets
 
 import exceptions
 from internal import get_manager
@@ -188,8 +188,8 @@
 	as attribute B{event_mapper}.
 
 	This instance handles all necessary house-keeping.
-	Such an event mapper can be either *attached* or
-	*detached*. In its attached state an L{EventListener}
+	Such an event mapper can be either C{attached} or
+	C{detached}. In its attached state an L{EventListenerBase}
 	is added to the Guichan widget and will redirect
 	the events to the callbacks.