Regardless of backwards compatibility issues, having a default alpha value
of 0 just seems completely wrong to me, and completely non-intuitive.
largely because in a 24-bit context (like on the web), I would always be
writing #RRGGBB, and would never even consider adding in an alpha. So my
brain has naturally gotten a lot of experience associating specifying RGB
with no A as meaning a solid color.
meaning I would definitely say having a default alpha of 0 in any case is a
bug. period.
On Sun, Aug 17, 2008 at 7:45 PM, Nicholas Dudfield <[EMAIL PROTECTED]>wrote:
> I will update the tests.
>
> If the new Color.__doc__ claims case insensitivity then I will put in a
> failing test.
>
> The author of the module wrote some tests for webstyle arguments to the
> Color constructor that explicitly tested for 0 as the default alpha so I'm
> not sure there.
>
> Actually there seems to be some internal inconsistencies as:
>
> In [2]: pygame.Color(0,0,0)
> Out[2]: (0, 0, 0, 255)
>
> In [3]: pygame.Color("#000000")
> Out[3]: (0, 0, 0, 0)
>
> What is the policy regarding backwards compatibility with 1.7.1? Should I
> put in tests for the old functions as well?
>
> Summary:
>
> Color construction from string, case insensitivity
> WebStyle default alpha
> Module level functions
>
