Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!adt.UUCP!madd
From: madd@adt.UUCP (jim frost)
Newsgroups: comp.windows.x
Subject: Re: A developer's view of the X fill policy
Message-ID: <8901051457.AA19767@adt.uucp>
Date: 5 Jan 89 14:57:57 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 33


>actually I meant what border_fill (your new field) gets used
>to define the wide outline?

I don't understand the question.  The border ought to be defined using
the normal line description fields of the GC (line_width, line_style,
join_style, cap_style) with the exception of fill_style which should
be assumed to be FillSolid so that the border will be unbroken.

I've given it some more thought and I don't think it would be
necessary to add a new field.  Instead, fill_rule could have the
following values:

	EvenOddRule
	WindingRule
	UnborderedEvenOddRule
	UnborderedWindingRule
	BorderedEvenOddRule
	BorderedWindingRule

I really like this idea better since there wouldn't be any changes to
the structures.

Another idea would be to treat fill_rule as a bit field.  This would
be backward compatible if you did something like the following:

	#define EvenOddRule    0x0
	#define WindingRule    0x1
	#define UnborderedRule 0x2
	#define BorderedRule   0x4

jim
madd@bu-it.bu.edu