Description
In short, I would like to just be able to call surface.blit(other_surface) instead of surface.blit(other_surface, (0, 0)).
I have been meaning to ask for this for a while. The major use case for this, at least in my code, is when applying effects to entire surfaces, like darkening by making a grey surface and then blitting it onto another surface with pygame.BLEND_RGB_MULTIPLY, or drawing a blackish 'fog-of-war' over the map on screen. A few ack, grep, and wc calls tell me that in my current pygame project, 11 of 42 blit calls use (0, 0) as their dest argument, and the rest are almost all pygame.Rect objects being passed in instead.
Description In short, I would like to just be able to call
surface.blit(other_surface)instead ofsurface.blit(other_surface, (0, 0)).I have been meaning to ask for this for a while. The major use case for this, at least in my code, is when applying effects to entire surfaces, like darkening by making a grey surface and then blitting it onto another surface with
pygame.BLEND_RGB_MULTIPLY, or drawing a blackish 'fog-of-war' over the map on screen. A fewack,grep, andwccalls tell me that in my current pygame project, 11 of 42 blit calls use(0, 0)as theirdestargument, and the rest are almost allpygame.Rectobjects being passed in instead.