Okay, cool. I'm only calling draw() on single VertexLists for prototyping, so I'll be sure to look into using batches in the future.
On Oct 21, 5:42 pm, "Alex Holkner" <[EMAIL PROTECTED]> wrote: > On Tue, Oct 21, 2008 at 10:14 AM, Mike Wyatt <[EMAIL PROTECTED]> wrote: > > > Why is the primitive mode passed to a vertex list's draw method, > > instead of the constructor? I don't see how the same vertex data > > could be used for multiple primitive modes, so why not specify the > > mode in the ctor and not worry about it later? This isn't a critical > > issue, but it is a mild annoyance to change two separate areas of code > > when I change the vertex data and primitive mode of a given > > VertexList. > > It's a design flaw. VertexLists are primarily designed to belong to > batches, and are aggregated into VertexDomains, which are in turn > aggregated into a Batch, which sorts the domains by primitive mode and > state. In this case the mode would be redundant in VertexList. > > The methods to draw VertexLists independently of batches were added > after the Batch/VertexDomain organisation was finished, and, due to > their poor performance, were not intended to be widely used. Of > course, now that you're using them, you're exposing the design flaw; > but it's unlikely to get fixed unless there's a major overhaul of all > of pyglet.graphics. > > 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 -~----------~----~----~----~------~----~------~--~---
