John Hunter wrote:
>> mean "do the default". The hack workaround we use here is to
>> set 'None' (the string) rather than None itself. Ugly, yes.
> and really, really prone to error. If you need to use
> a string, use something else, like perhaps
How is it really prone to error -- I would think that if the user pass
es 'None', the string, for a color arg, there aren't too many
>> The real root of the problem is that renderer.draw_polygon(gc,
>> rgbFace, tverts) is overloaded to support edge and face drawing
>> in one function call.
> That's actually a good thing. I like to think of a
> polygon with a border a single object, and it can
> dome in handy if you want to do something like draw a
> polygon with a border that is
> semi-transparent. drawing the fill and the stroke
> independently doesn't work right. I was recently
> messing around with this in Cairo, and it's a pain
> int eh *&^, but it can be done right, but it's up to
> the back-end to figure out how.
You may be right -- it may be a good thing -- what we need is a clear
way to say "edge on" or "face on". One way is to figure out a way to
do it with the color specification itself ('None' or something like
it). Another way is to add boolean flags to the gc object...