[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Accidentals Patch 1.5.24
From: |
Han-Wen Nienhuys |
Subject: |
Re: Accidentals Patch 1.5.24 |
Date: |
Wed, 5 Dec 2001 15:51:13 +0100 |
address@hidden writes:
> HN> As I said earlier, I would like to remove the broken tie-thing, as it
> HN> is hairy and be difficult to support properly. If we do remove it, we
> HN> must however have a mechanism to get the same result.
>
> I'll leave it until the \break command works again.
> Then we must take a look.
> I am pretty sure that when it is first out, it'll never be back in, so we have
> to be REALLY sure that there's nothing we can do.
> It is a big problem to leave it to the user to get the broken-tie-accidentals
> right. Just think about stuff like supporting both a4 and letter, like
> extracting individual parts, like typesetting the score in a smaller
> font...
Ok, point taken. We have to let it stay in. Nevertheless, it is a very
hairy aspect.
> Which is ugly. Doing an arbitrary lazyness would require an entire array of
> signatures... Or alternatively that all entries in the signature remember how
> old they are - which would require quite a lot of code and not really giving
> much new flexibility.
I was thinking of the second option. I agree that it would take hassle.
>
> I think that the entire lazyness thing is strange (I will usually run with
> onemeasure = #f - or infinite lazyness) - and the only reason I implemented
> it is that Stone mentioned it.
Ok.
i
> HN>> with note heads), this needs to be in a context higher than
> HN>> Tie_engraver. FIXME",
> HN>> /* creats*/ "Accidentals",
> HN>> /* acks */ "rhythmic-head-interface tie-interface arpeggio-interface",
> HN>> -/* reads */ "localKeySignature forgetAccidentals noResetKey
> HN>> autoReminders", +/* reads */ "localKeySignature lazyKeySignature
> HN>> forgetAccidentals oneMeasureLazy extraNatural autoAccidentals
> HN>> autoCautionaries",
> HN>> /* write */ "");
> HN>
> HN> this should have a list of properties written using set_property().
>
> ???? I am not having access to the sources right now, but I don't just
> understand what you mean.
if the engraver does
daddy_trans_l_->set_property("fooBar")
then macro argument should have
/* write */ "fooBar"
--
Han-Wen Nienhuys | address@hidden | http://www.cs.uu.nl/~hanwen/