I agree. I would say it's good practice for developers to test their applications with newer Cocos versions anyway, so as long as this change is documented (I'd say this thread already qualifies) it's a quick fix for them, in case they use it.
Regards, Ivo On Thu, 2012-04-26 at 09:01 -0700, Winston Wolff wrote: > I say go ahead--we need 1.2dev support because it works with 64-bit python. > > -ww > > On Apr 26, 2012, at 6:37 AM, claudio canepa wrote: > > > Short version: > > > > To fix the recorder functionality in cocos that works with pyglet 1.1.4 but > > fails with pyglet 1.2dev, and also add some autotesting functionality, > > better code can be done if I move ScreenReaderClock from director to a new > > module custom_clock. > > > > This will break user code that relies on ScreenReaderClock to be in > > director, ie subclassing it or directly instantiating it. > > I think it is unlikely the direct use case, so may be I can spare the > > overhead and ugliness of deprecation warnings and duplicate code. > > > > Updating problematic user code should be as simple as > > director.ScreenReaderClock --> cocos.custom_clocks. ScreenReaderClock > > > > Any feedback ? > > > > Details can be seen at issues 175, 177 > > http://code.google.com/p/los-cocos/issues/detail?id=175 > > http://code.google.com/p/los-cocos/issues/detail?id=177 > > > > claudio > > > > -- > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "cocos2d discuss" 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/cocos-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" 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/cocos-discuss?hl=en.
