Bruce, Neon, Those are good arguments for leaving it as-is. Greg, I don't know if an initialization option would be wise, just due to the large amount of options we would have to consider.
Adding this to a section in the documentation seems to be the best option. There are a few performance tidbits written about in various sections, but it would be nice to consolodate them together, and then link back to the appropriate section where applicable. Other things, such as the general usage of Batches and Groups would also be good to put in there. The Doc generation inself needs an overhaul. API docs in particular are broken, due to lots of "is_epydoc" issues that have popped up. Some popular IDEs were choking on pyglet's usage of those flags in the modules for documentation. The programming guide is not specifically affected by this, but docs as a whole will need a little love. On Sunday, May 27, 2018 at 9:14:43 AM UTC+9, Greg Ewing wrote: > > Bruce Smith wrote: > > - some people understand all this and can optimize the settings for > their > > application; > > > > - but for people who don't understand it all ... the kind of bugs > they'll get > > ... might seem mysterious to them > > Maybe provide an initialisation option that lets you choose > between "most accurate rendering" and "highest frame rate", > with a few words in the docs about the implications of > choosing one or the other. > > -- > Greg > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
