Re: Some code for polygons

2006-04-12 Thread David Feuer
On 4/12/06, Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > David Feuer writes: > > > The easiest way to keep this working the same as it does now is to > > name my new functions filled-polygon and retain the old (really > > simple) polygon drawers in the backends. > > Hmm. I'd much rather just hav

Re: Some code for polygons

2006-04-12 Thread Jan Nieuwenhuizen
David Feuer writes: > The easiest way to keep this working the same as it does now is to > name my new functions filled-polygon and retain the old (really > simple) polygon drawers in the backends. Hmm. I'd much rather just have a simple dedicated white-triangle function, if we must. > The poly

Re: Some code for polygons

2006-04-12 Thread Juergen Reuter
Hi, maybe I should also comment on this topic, since I originally contributed the whole polygon stuff in order to implement clusters, and thus still feel (very) little responsible for it. ;-) As for the triangle, yes, I also think it _is_ abuse to use the blot-diameter in order to control th

Re: Some code for polygons

2006-04-12 Thread David Feuer
On 4/12/06, Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > Indeed; no need for an assert. But in that case ... found it > > define-markup-command.scm: > (define-markup-command (triangle layout props filled) (boolean?) > "A triangle, filled or not" > > we use it to draw `white' triangles for chor

Re: Some code for polygons

2006-04-12 Thread Jan Nieuwenhuizen
David Feuer writes: > I'm not sure where you'll add it. The code in lookup.cc always calls > the scheme function with filled?=#t Indeed; no need for an assert. But in that case ... found it define-markup-command.scm: (define-markup-command (triangle layout props filled) (boolean?) "A triangl

Re: Some code for polygons

2006-04-12 Thread David Feuer
On 4/12/06, Jan Nieuwenhuizen <[EMAIL PROTECTED]> wrote: > Ok, I'll add an assert in the c++ code and remove the parameter to match > your next polygon scheme code. I'm not sure where you'll add it. The code in lookup.cc always calls the scheme function with filled?=#t > > I would suggest that

Re: Some code for polygons

2006-04-12 Thread Jan Nieuwenhuizen
David Feuer writes: > I didn't even think about that. I just wrote the functions > and gave them the interface that made the most sense to me at the > time. I'll change it in the next version. Ok. >> Btw, what about the the filled? parameter, is it never used? > > As far as I can tell from gre

Re: Some code for polygons

2006-04-12 Thread Jan Nieuwenhuizen
David Feuer writes: > I would greatly appreciate some help changing the code in lookup.cc > to match my new drawing procedures. I'm still not sure whether the > polygon drawer should take a list of vertices or an array of > vertices. It seems that you changed the polygon interface from (prefixin

Re: Some code for polygons

2006-04-11 Thread Johannes Schindelin
Hi, On Tue, 11 Apr 2006, Jan Nieuwenhuizen wrote: > I currently have very little time to work on Lily related stuff. That's a pity. > I have a daytime job, two small twin girls and just bought a house :-) Congratulations! Ciao, Dscho ___ lilypon

Re: Some code for polygons

2006-04-11 Thread Jan Nieuwenhuizen
David Feuer writes: > I've written code to do rounded polygons /properly/ in both PostScript > and SVG. The SVG was a bit tricky because SVG doesn't have > PostScript's arct. I would greatly appreciate some help changing the > code in lookup.cc to match my new drawing procedures. That's great.

Some code for polygons

2006-04-10 Thread David Feuer
I've written code to do rounded polygons /properly/ in both PostScript and SVG. The SVG was a bit tricky because SVG doesn't have PostScript's arct. I would greatly appreciate some help changing the code in lookup.cc to match my new drawing procedures. I'm still not sure whether the polygon draw