On Mon, Feb 9, 2009 at 1:47 AM, sol <[email protected]> wrote:
>
> So in 1.0, it would 'push', but in the wrong order? Where as in 1.1 it
> always sets? This this a correct way of me stating it?
The 1.0 behaviour was basically broken. e.g.
class Foo(EventDispatcher):
def on_bar(self):
print 'A'
foo = Foo()
foo.push_handler(on_bar=lambda: print('B'))
@foo.event
def on_bar():
print 'C'
In this case C replaces A, but ignores the effects of B; so the
handlers will be called in order B, C.
In pyglet 1.1 C replaces B, so the order is C, A.
Alex.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
