On Mar 5, 11:43 pm, "Alex Holkner" <[EMAIL PROTECTED]> wrote: > Does this feel more palatable? > > class ParticleSystem(object): > def update(self, dt): > self.next_dt = dt > > def draw(self): > for particle in self.particles: > # update and draw with self.next_dt
Yes, that is exactly what I'm planning to try next. And its not really about performance (I wouldn't choose Python in that case). It is more about finding best way to express ideas in code. I am not sure yet, but it *feels* more natural for me to control particle state in its drawing routine. Time will show. This whole thing is just a test bed for my humble gamedev ideas. I general, as I said before, I am do very like the idea to separate 'update' and 'drawing' code for game objects. -- serg. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
