[pygame] Locking surfaces and cursors

[David Clark <silenus@telus.net>]

Jan Ekholm writes:

 > 
 > Maybe get_at() could do an automatic lock/unlock when used? Then the user
 > would not have to worry about it. Or is this a too big performance hit if
 > it is called repeatedly?
 > 

I'd vote for just leaving things the way they are, and adding a note
to the documentation for set_at, saying that fill may be faster. I've
only tested this on two platforms; it may not hold for everyone.

-- 
David Clark - silenus@telus.net
Microsoft isn't the answer, it's the question.
Linux is the answer.
Microsoft is never the answer, unless the question is
"What isn't the answer?"

____________________________________
pygame mailing list
pygame-users@seul.org
http://pygame.seul.org