On Fri, 5 May 2006 18:43, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > First of all, instead of penalty, breakable and page-penalty, we now
> > have: break-penalty, break-permission
> > page-break-penalty, page-break-permission
> > page-turn-penalty, page-turn-permission
>
> sounds good.
>
> > w
Erik Sandberg wrote:
Modified files:
. : ChangeLog
lily : context.cc global-context.cc
lily/include : context.hh global-context.hh lily-proto.hh
scm: lily.scm
Added files:
lily : dispatcher-scheme.cc dispatcher.cc listener.cc
Erlend Aasland wrote:
I agree. But the problem is more about what variables to modify. It
appears to me like dim_ contains the bounding box, but when I modify it,
the rotated stencils are misplaced.
strange. are you sure you're not seeing artefacts of the fact that
placements algorithms look
Joe Neeman wrote:
On Fri, 5 May 2006 18:43, Han-Wen Nienhuys wrote:
Joe Neeman wrote:
First of all, instead of penalty, breakable and page-penalty, we now
have: break-penalty, break-permission
page-break-penalty, page-break-permission
page-turn-penalty, page-turn-permission
sounds good.
wher
On 5/5/06, Johannes Schindelin <[EMAIL PROTECTED]> wrote:
On Fri, 5 May 2006, Erlend Aasland wrote:> I agree. But the problem is more about what variables to modify. It appears> to me like dim_ contains the bounding box, but when I modify it, the> rotated stencils are misplaced.
Ah. I understand. Y
Hi,
On Fri, 5 May 2006, Erlend Aasland wrote:
> I agree. But the problem is more about what variables to modify. It appears
> to me like dim_ contains the bounding box, but when I modify it, the
> rotated stencils are misplaced.
Ah. I understand. You probably have to adjust the offsets, too?
C
Hi JohannesOn 5/5/06, Johannes Schindelin <[EMAIL PROTECTED]> wrote:
I don't know about dim_, but the easiest way to find the new bounding boxis to rotate all four edges of the original bounding box, and take theminima and maxima of the results as new bounds.Of course, you could try to be clever an
Hi,
On Fri, 5 May 2006, Erlend Aasland wrote:
> But, I'm having some problems with adjusting the bounding box. Should it not
> be sufficient to modify dim_ in the stencil?
I don't know about dim_, but the easiest way to find the new bounding box
is to rotate all four edges of the original bound
Hi Han-WenI've had very little time to do coding the past two days, so I've only managed to do a little bit more on this rotation thing.Rotation is now specified as #'(degrees x y) where x and y are relative to the extent of the grob (
i.e. (0,0) is center and (1,1) is upper right corner...). This
On Fri, 5 May 2006 18:43, Han-Wen Nienhuys wrote:
> Joe Neeman wrote:
> > First of all, instead of penalty, breakable and page-penalty, we now
> > have: break-penalty, break-permission
> > page-break-penalty, page-break-permission
> > page-turn-penalty, page-turn-permission
>
> sounds good.
>
> > w
Han-Wen Nienhuys writes:
> has this been a real problem or a preemptive strike? I wonder whether
> spammers also harvest CVS repositories.
As as spammer, I would ;-)
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.
Graham Percival wrote:
Erik stopped including submitter's emails in the bug CVS to avoid them
getting spammed; he simply kept a mailbox of bug emails, and when an
has this been a real problem or a preemptive strike? I wonder whether
spammers also harvest CVS repositories.
--
Han-Wen Nien
On 5-May-06, at 1:32 AM, Han-Wen Nienhuys wrote:
Graham Percival wrote:
When we set up the bug tracker, could each bug have a "submitter's
email" field, which is only viewable by admins? We should keep track
of who submitted each bug so that they can be notified when it's
fixed, but we don'
Joe Neeman wrote:
First of all, instead of penalty, breakable and page-penalty, we now have:
break-penalty, break-permission
page-break-penalty, page-break-permission
page-turn-penalty, page-turn-permission
sounds good.
where XXX-permission can be 'allow, 'force or 'forbid.
can you drop the
Graham Percival wrote:
When we set up the bug tracker, could each bug have a "submitter's
email" field, which is only viewable by admins? We should keep track of
who submitted each bug so that they can be notified when it's fixed, but
we don't want those addresses spammed.
The submitter's ad
15 matches
Mail list logo