Inconsistency of `font` and `draw` module when handling hex color

[yunline]

import pygame

pygame.init()

font = pygame.font.Font(None, 60)

sf = pygame.display.set_mode((640,480))

sf.fill("black")

COLOR_HEX = 0x00ff00ff
COLOR_DEC = (0, 255, 0, 255)


font_sf1 = font.render("test", True, COLOR_HEX)
sf.blit(font_sf1, (10,10))
pygame.draw.rect(sf, COLOR_HEX , (100,10,50,50))
pygame.draw.circle(sf, COLOR_HEX, (200,35), 30)

font_sf2 = font.render("test", True, COLOR_DEC)
sf.blit(font_sf2, (10,100))
pygame.draw.rect(sf, COLOR_DEC , (100,100,50,50))
pygame.draw.circle(sf, COLOR_DEC, (200,125), 30)

pygame.display.flip()

while 1:
    pygame.event.get()

Result:

Expected:

[ankith26]

This is a known issue and a common source of confusion. Passing int does not mean it is always interpreted as 0xRRGGBBAA (the same is documented in the Color constructor docs). If you want that, you should pass the same thing but as a string ("0xRRGGBBAA" or even "#RRGGBBAA"). The problem here (that I plan to fix) is the inconsistency of some functions interpreting ints as mapped colors and some not. Though I'm sure "fixing" this will break someones code somewhere, so maybe the fix should be instead documenting this better? IDK, open to discussion and more inputs on this

[ankith26]

See my last comment in #2336 where I elaborated a bit more

[Starbuck5]

Actually there could be more discussion this, so I won't close.

Is this something we could do in a pygame-ce 3.0? Fix an incongruity that technically breaks back-compat but in a very minor way that most won't notice?