On Thu, 13 Apr 2000, [EMAIL PROTECTED] wrote:
> On 12 Apr 2000, Lars Clausen wrote:
>
>> That's how it was, until today. I also implemented a proper
>> interior-point detection algorithm (both, in fact, though I haven't
>> tested the winding version). Check an update.
>>
> Are you sure you have commited this? This is the change I made to
> polyshape.c:
You were right -- I added the Changelog entry, but never committed.
Anyway, you code is slightly nicer. I added a division-by-zero special
case, though.
>> Very nice! That means once the polygon is ready (still have problems
>> with the connectionpoints), it'll be trivial to do the beziergon.
>>
>> One thing about bezier{line,gon}: The two control lines around a point
>> are currently joined together. Is anybody interested in having the
>> ability to break them apart so they can move independently? (Or did I
>> ask this already?) It's almost, but not quite, trivial.
>>
> That is probably a good idea. There are three ways to handle the control
> lines - cusp (the two control points are independent), smooth (two
> control points are on the same line) and symmetric (the current
> behaviour). It would probably be nice to allow the user to change the
> behaviour for each point on a bezierconn.
So in smooth, you can move the controls in and out along a line, but
they're always on one line. Neat.
> To keep compatibility, symmetric would have to be the default.
Yes. Not just for compatibility, also because I think most users would use
symmetric.
-Lars
--
Lars Clausen (http://shasta.cs.uiuc.edu/~lrclause) | H�rdgrim of Numenor
"I do not agree with a word that you say, but I | Retainer of Sir Kegg
will defend to the death your right to say it." | of Westfield
--Evelyn Beatrice Hall paraphrasing Voltaire | Chaos Berserker of Khorne
