Hello,
Here is the current patch countdown list. The next countdown will be on
April 25th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
__
Push: No patches to push at this time.
Countdown:
4828 Allow ove
https://codereview.appspot.com/295970043/diff/1/lily/ledger-line-spanner.cc
File lily/ledger-line-spanner.cc (right):
https://codereview.appspot.com/295970043/diff/1/lily/ledger-line-spanner.cc#newcode221
lily/ledger-line-spanner.cc:221: int len = scm_to_int (scm_length
(posns));
scm_ilength alr
2016-04-21 12:14 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> 2016-04-21 10:55 GMT+02:00 Federico Bruni :
>>> Il giorno gio 21 apr 2016 alle 10:47, David Kastrup ha
>>> scritto:
Works
and everything, but since I've been locked out of git-cl temporarily by
some Ubuntu
2016-04-22 8:12 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> Folks,
>>
>> we have event-chord-wrap! and is does the job it was designed for pretty
>> good.
>>
>> Though, sometimes too much: If a single note has instructions for
>> (stroke-)fingerings and or string-numbers it would make
Thomas Morley writes:
> 2016-04-22 8:12 GMT+02:00 David Kastrup :
>>
>> If you want to mimic this exactly, you need to retain all articulations
>> for which there are no listeners (that's what the
>> Rhythmic_music_iterator does), but the presence of listeners is not
>> established at the point o
Hi folks,
I am currently doing pitch 2 at first-class Scheme engravers and am
sorely tempted to scratch the whole macro-based mess and do it via
inheritance and templates.
Now the sore point is that the basic type for which Scheme functions are
defined is that of a Translator. And Engravers and
On 4/22/16 6:07 AM, "lilypond-devel on behalf of David Kastrup"
wrote:
>
>Hi folks,
>
>I am currently doing pitch 2 at first-class Scheme engravers and am
>sorely tempted to scratch the whole macro-based mess and do it via
>inheritance and templates.
>
>Now the sore point is that the basic type f
David Kastrup wrote Friday, April 22, 2016 1:07 PM
> I am currently doing pitch 2 at first-class Scheme engravers and am
> sorely tempted to scratch the whole macro-based mess and do it via
> inheritance and templates.
>
> Now the sore point is that the basic type for which Scheme functions are
"Trevor Daniels" writes:
> Not really an objection; just a thought. I can't comment on the
> technicalities, and I've every confidence you can carry this through,
> but I wonder about the position of existing compositions that include
> custom C++ engravers in the old (i.e. current) style.
If p
> I am currently doing pitch 2 at first-class Scheme engravers and am
> sorely tempted to scratch the whole macro-based mess and do it via
> inheritance and templates.
Sounds OK to me. Thanks for working on this.
Werner
___
lilypond-devel mailin
Arghh! Tweaks and workarounds!
"For a contemporary glissando from a note, you can use hideNote and
cadenzaOn/Off". Except I've tried it and the side effects have buggered
everything else up !!!
As soon as you start combining voices - like I separate markups, time
signatures, etc from notes -
Patch set 2, based on David's Feedback.
-Paul
https://codereview.appspot.com/295970043/diff/1/lily/ledger-line-spanner.cc
File lily/ledger-line-spanner.cc (right):
https://codereview.appspot.com/295970043/diff/1/lily/ledger-line-spanner.cc#newcode221
lily/ledger-line-spanner.cc:221: int len = s
Even better, use scaled notes:
/\relative c' {
\repeat unfold 2 {
g''2*1/2 \glissando \once \hideNotes g,4
}
}/
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Notation-manual-1-3-3-Expressive-marks-as-lines-glissandi-tp189878p189881.html
Sent from the Dev mailing li
> On Apr 22, 2016, at 8:07 AM, David Kastrup wrote:
>
> I am currently doing pitch 2 at first-class Scheme engravers and am
> sorely tempted to scratch the whole macro-based mess and do it via
> inheritance and templates.
I can’t comment on the implementation questions, but it will be great to h
Am 23.04.2016 um 07:09 schrieb Paul Morris:
> (Also, while I’m at it, your recent dotted list work, allowing "violin.1”
> etc, is also really nice.)
Oh, I seem to have missed this, but that's great. Finally we can write
indexed parts/variables!
Thanks for adding this, David.
Best
Urs
15 matches
Mail list logo
