On 10/25/07, Casey Duncan <[EMAIL PROTECTED]> wrote: > On Oct 25, 2007, at 9:56 AM, Ian Mallett wrote: > surface.get_at() can be kinda slow, and typically sequence item > access is faster in python then a function call anyway. > Regardless, I wouldn't worry about it unless it helps makes the code > simpler or profiling shows you that using get_at() is slowing you > down too much. It's slowing it down some, but the speed is fine. It's other people running my program that I'm worried about. My computer can do 256 squared calls to surface.get_at() in about 30 seconds, but it is pretty new. Ian
- [pygame] image.load() -->> array? AlgoMantra
- Re: [pygame] image.load() -->> array? Casey Duncan
- Re: [pygame] image.load() -->> array? AlgoMantra
- Re: [pygame] image.load() -->> array? Casey Duncan
- Re: [pygame] image.load() -->> ar... AlgoMantra
- Re: [pygame] image.load() -->&g... Ian Mallett
- Re: [pygame] image.load() --&g... AlgoMantra
- Re: [pygame] image.load() --&g... Casey Duncan
- Re: [pygame] image.load() ... Ian Mallett
- Re: [pygame] image.load() ... Casey Duncan
- Re: [pygame] image.load() ... Ian Mallett
- Re: [pygame] image.load() ... Luke Paireepinart
- Re: [pygame] image.load() ... Ian Mallett
- Re: [pygame] image.load() ... Patrick Mullen
- Re: [pygame] image.load() ... Greg Ewing
- Re: [pygame] image.load() ... Greg Ewing
- Re: [pygame] image.load() ... Ian Mallett
- Re: [pygame] image.load() ... Brian Fisher
- Re: [pygame] image.load() ... Ian Mallett