Yeah, I have no windows dev environment either.  I can have a chat with the
code, but it sounds like something obscure...and I have no idea what the
windows equivalent of valgrind is.


On Mon, May 6, 2013 at 12:04 AM, Nathan <[email protected]> wrote:

> On Sun, May 5, 2013 at 5:56 PM, Andre D <[email protected]> wrote:
>
>> Oh, the leak is only on windows?  Good luck ;)
>>
>>
> Er, ya, valgrind's web site says "windows support is not planned...".  And
> I don't know much about windows development in the first place.  I
> certainly am not about to spend a fortune for Microsoft's proprietary
> development tools and weeks figuring them out just to be nice and fix this
> bug.
>
> Still, I learned a little bit about GDI and GDI+.  Mostly that their API
> was designed by a committee of sadistic masochists.  But hey, at least
> Google could find the MSDN documentation and it was fairly decently
> documented.
>
> The win32 pyglet files are much longer than the corresponding OS X ones.
>  I was particularly amused by several of the comments like this one in
> pyglet/font/win32.py:
>
> # Windows GDI+ is a filthy broken toy.  No way to measure the bounding
> # box of a string, or to obtain LSB.  What a joke.
>
> ~ Nathan
>
> --
> 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 http://groups.google.com/group/pyglet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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 http://groups.google.com/group/pyglet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to