Just tested commenting out code in pyglet/graphics/vertexdomain.py:
#elif primcount == 1:
# # Common case
# glDrawElements(mode, sizes[0], self.index_gl_type,
# self.index_buffer.ptr + starts[0])
this forces it to use glMultiDrawElements, and I'm not able to crash
the demo on the computer I originally ran into a problem with.
It happily deletes vertices all day.
does this help at all? Is this suggesting card/driver problem, or
32/64 problem? I'm not familiar enough with OpenGL to know what the
significance of MultiDrawElements vs DrawElements is....
I'll see what I can find.
Joe
On Dec 20, 12:10 am, Joe Cross <[email protected]> wrote:
> Thanks! I have properties in there, they're below the get/set
> methods.
> This was a quick demo, so I used PyDev's auto naming, and forgot to
> privatize them. But yes, there's properties in there =)
>
> On Dec 19, 10:23 pm, Jake b <[email protected]> wrote:
>
>
>
>
>
>
>
> > There's a property() decorator as of python2.6
> > :http://docs.python.org/library/functions.html#property
>
> > On Sun, Dec 4, 2011 at 10:58 AM, Joe Cross <[email protected]> wrote:
> > > Hello,
>
> > > Much simpler demo here.
>
> > >https://github.com/numberoverzero/BatchDrawExample
>
> > > Simply import Example and click around.
>
> > > Main runs the window and update, and Shape takes care of rectangle
> > > updating.
> > > The reason for getters/setters on each variable is so that when they
> > > change, verts are updated correctly.
>
> > > --
>
> > Jake
--
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.
