I've just committed rev 807, with working BatchNode and BatchableNode. A couple of notes about their new implementation:
- Nested z-layers are blended into groups, so if a BatchNode has a child A at z=0 and child B at z=1, and B has child C at z=-1, A and C end up in the same pyglet Group. As having a small amount of groups is good I think this is better than creating separate groups for each. - All descendants of a BatchNode have their position taken relative to the BatchNode, not their immediate parent. This for me makes sense: as you draw a batch completely you can't apply transformations between one child an another, so I can't imagine any way of making nested transformations work while keeping the performance benefits of batches. I've added three tests to show batches at work (test_bath[1,2,3].py), if you want to give it a quick spin. In test_batch.py try changing the instantiation of the TestBatch layer for a TestNoBatch layer, to see how you FPS and CPU usage swap :-) Cheers, achuni --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
