August'24: Kamaelia is in maintenance mode and will recieve periodic updates, about twice a year, primarily targeted around Python 3 and ecosystem compatibility. PRs are always welcome. Latest Release: 1.14.32 (2024/3/24)

Kamaelia.UI.Pygame.Button

Pygame Button Widget

A button widget for pygame display surfaces. Sends a message when clicked.

Uses the Pygame Display service.

Example Usage

Three buttons that output messages to the console:

button1 = Button(caption="Press SPACE or click",key=K_SPACE).activate()
button2 = Button(caption="Reverse colours",fgcolour=(255,255,255),bgcolour=(0,0,0)).activate()
button3 = Button(caption="Mary...",msg="Mary had a little lamb", position=(200,100)).activate()

ce = ConsoleEchoer().activate()
button1.link( (button1,"outbox"), (ce,"inbox") )
button2.link( (button2,"outbox"), (ce,"inbox") )
button3.link( (button3,"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 an output "msg" is not specified, the default is a tuple ("CLICK", id) where id is the self.id attribute of the component.
  • A pygame keycode can be specified that will also trigger the button as if it had been clicked
  • you can set the text label, colour, margin size and position of the button
  • the button can have a transparent background
  • you can specify a size as width,height. If specified, the margin size is ignored and the text label will be centred within the button

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.Button.Button

class Button(Axon.Component.component)

Button(...) -> new Button 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))
  • key -- if not None, pygame keycode to trigger click (default=None)
  • transparent -- draw background transparent if True (default=False)
  • size -- None or (w,h) in pixels (default=None)

Inboxes

  • control : For shutdown messages
  • callback : Receive callbacks from Pygame Display
  • inbox : Receive events from Pygame Display

Outboxes

  • outbox : button click events emitted here
  • signal : For shutdown messages
  • display_signal : Outbox used for communicating to the display surface

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][, key][, 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