Kamaelia docs : Kamaelia.UI.Pygame.EventHandler

Pygame event handling

A simple framework for handling pygame events. Reimplement the appropriate stub method to handle a given event.

Example Usage

Detecting key presses and mouse button depressions and releases::
class MyEventHandler(EventHandler):
def __init__(self, target):
super(MyEventHandler,self).__init__() self.target = target
def keydown(self, key, mod, where):
print "Keypress '"+key+"' detected by "+where
def mousebuttondown(self, pos, button, where):
print "Mouse button depressed"
def mousebuttonup(self, pos, button, where):
print "Mouse button released"

How does it work?

Implement your event handler by subclassing EventHandler and reimplementing the stub methods for the particular events you wish to handle.

The code that reads the events from pygame should pass them one at a time to EventHandler by calling the dispatch(...) method.

The optional 'trace' argument to the initialiser, when non-zero, causes the existing stub handlers to print messages to standard out, notifying you that the given event has taken place.


Feedback

Got a problem with the documentation? Something unclear that could be clearer? Want to help improve it? Constructive criticism is very welcome - especially if you can suggest a better rewording!

Please leave you feedback here in reply to the documentation thread in the Kamaelia blog.

-- Automatic documentation generator, 05 Jun 2009 at 03:01:38 UTC/GMT


Kamaelia is an open source project originated from and guided by BBC Research. For more information browse the site or get in contact.

This is an ongoing community based development site. As a result the contents of this page is the opinions of the contributors of the pages involved not the organisations involved. Specificially, this page may contain personal views which are not the views of the BBC. (the site is powered by a wiki engine)

(C) Copyright 2008 Kamaelia Contributors, including the British Broadcasting Corporation, All Rights Reserved.

This web site is powered by the same code created for the bicker manor project. For more details, contact Michael Sparks at BBC Research directly (cf contact)