Popular recipes tagged "event" but not "gtk"

Simple signal library, similar to PyQT signals (Python)

2017-04-01T21:11:50-07:00

Python recipe 580764 by Miguel Martínez López (event, pubsub, signal). Revision 11.

Simple signal library similar to PyQT signals. Signals helps to decouple code in GUI applications. This code could be used in Tkinter applications for example.

Inspired and based in these other modules:

https://github.com/shaunduncan/smokesignal

https://github.com/dgovil/PySignal

https://github.com/jek/blinker

Connect PyGTK object events to class methods automatically (Python)

2011-02-19T17:50:42-08:00

Python recipe 577577 by Pavel Krc (automate, connect, decorator, event, pygtk). Revision 2.

A module that allows you to not to repeat yourself (DRY) while writing typical PyGTK constructions (an object containing PyGTK widgets with its methods servicing widget events) by calling connect() automatically. See docstring.

Observer Design Pattern for python gevent coroutine package (Python)

2010-12-08T08:33:30-08:00

Python recipe 577491 by Andrey Nikishaev (event, gevent, observer, python).

This is simple implementation of the observer design pattern. Acting as a registration hub, it fires events when requested. Also i have gevent.Timeout like interface in situations when you need to run event-method in the same greenlet. Example:

e = Observer()
ev = e.wait('kill')
try:
    gevent.sleep(3)
except FiredEvent:
    print 'Fired!'
else:
    print 'Not Fired!'
finally:
    ev.cancel()

But rememeber, if you are using subscribe method, event-method will be executed in another greenlet.

Simple event dispatcher (Python)

2010-10-19T21:18:45-07:00

Python recipe 577432 by Daniele Esposti (dispatcher, event).

An example of a simple event dispatcher mini-framework

Flexible observer pattern implementation (Python)

2012-12-06T19:23:11-08:00

Python recipe 576962 by Glenn Eychaner (event, observer, pattern, publish, subscribe, threadsafe). Revision 16.

A simple, flexible, general-purpose observer pattern.

Observers can be callable objects or objects with a particular named method (handle_notify() by default). Events can be any object, and observers can select which events they are interested in receiving. Support for a number of different types of lightweight event objects is included.