April 2024 - This site, and Kamaelia are being updated. There is significant work needed, and PRs are welcome.

Kamaelia.UI.Pygame.Multiclick

Pygame Multi-click Button Widget

A button widget for pygame display surfaces. Sends a message when clicked. The message can be different for each mouse button.

Uses the Pygame Display service.

Example Usage

Three buttons that output messages to the console:

msgs = [ "button 1", "button 2", "button 3", "button 4", "button 5" ]
button1 = Button(caption="Click different mouse buttons!",msgs=msgs).activate()

ce = ConsoleEchoer().activate()
button1.link( (button1,"outbox"), (ce,"inbox") )

How does it work?

The component requests a display surface from the Pygame Display service component. This is used as the surface of the button. It also binds event listeners to the service, as appropriate.

Arguments to the constructor configure the appearance and behaviour of the button component:

  • If "msgs" is specified, then a different message can be specified for each mouse button. If it is not specified, then "msg" is used instead, for all buttons.
  • If an output "msg" is not specified, the default is a tuple ("CLICK", id) where id is the self.id attribute of the component.
  • you can set the text label, colour, margin size, size and position of the button
  • if you do not specify the size yourself, the size will default to fit the caption of the button.
  • the button can have a transparent background

If a producerFinished or shutdownMicroprocess message is received on its "control" inbox. It is passed on out of its "signal" outbox and the component terminates.

Upon termination, this component does not unbind itself from the Pygame Display service. It does not deregister event handlers and does not relinquish the display surface it requested.


Kamaelia.UI.Pygame.Multiclick.Multiclick

class Multiclick(Axon.Component.component)

Multiclick(...) -> new Multiclick component.

Create a button widget in pygame, using the Pygame Display service. Sends a message out of its outbox when clicked.

Keyword arguments (all optional):

  • caption -- text (default="Button <component id>")
  • position -- (x,y) position of top left corner in pixels
  • margin -- pixels margin between caption and button edge (default=8)
  • bgcolour -- (r,g,b) fill colour (default=(224,224,224))
  • fgcolour -- (r,g,b) text colour (default=(0,0,0))
  • msg -- sent when clicked (default=("CLICK",self.id)) of msgs is not specified
  • msgs -- list of messages. msgs[x] is sent when button X is clicked (default=None)
  • transparent -- draw background transparent if True (default=False)
  • size -- (width,height) pixels size of the button (default=scaled to fit caption)

Inboxes

  • control : Shutdown messages: shutdownMicroprocess or producerFinished
  • callback : Receive callbacks from Pygame Display
  • inbox : Receive events from Pygame Display

Outboxes

  • outbox : button click events emitted here
  • signal : Shutdown signalling: shutdownMicroprocess or producerFinished
  • display_signal : For sending signals to the Pygame Display

Methods defined here

Warning!

You should be using the inbox/outbox interface, not these methods (except construction). This documentation is designed as a roadmap as to their functionalilty for maintainers and new component developers.

__init__(self[, caption][, position][, margin][, bgcolour][, fgcolour][, msg][, msgs][, transparent][, size])

x.__init__(...) initializes x; see x.__class__.__doc__ for signature

blitToSurface(self)

Clears the background and renders the text label onto the button surface.

buildCaption(self, text)

Pre-render the text to go on the button label.

main(self)

Main loop.

waitBox(self, boxname)

Generator. yields 1 until data ready on the named inbox.

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