On Mon, Feb 16, 2015 at 11:46 AM, David Nalesnik
wrote:
> Spacing rods are created between columns--PaperColumn (PC) and
> NonMusicalPaperColumn (NMPC). The distance that these rods enforce is from
> the beginning of one column to the next. So, if we have two notes, there
> is a distance set b
Hi Werner,
On Mon, Feb 16, 2015 at 1:59 AM, Werner LEMBERG wrote:
DN wrote:
>
> > From your analysis it appear that LilyPond is taking the entire
> > NonMusicalPaperColumn into account rather than just the right
> > extent. I'll have a look. (This could be major!)
>
That's not quite it. A
>> In bar 2 you can see the effect of `minimum-length-after-break'.
>
> You mean bar 4--bar 2 is the default.
Of course. Typo.
>> Any chance to fix this? BTW, if you compare bar 2 with bar 6, you
>> see exactly the opposite effect w.r.t. the default tie length: with
>> a time signature the ti
Hi Werner,
On Sun, Feb 15, 2015 at 8:09 AM, Werner LEMBERG wrote:
>
> >> If it's convenient, have a look at the attached patch/sketch. It
> >> adds a property, minimum-length-left-broken, which lets you adjust
> >> broken bits that start a line.
> >
> > Excellent! What an improvement with just
>> If it's convenient, have a look at the attached patch/sketch. It
>> adds a property, minimum-length-left-broken, which lets you adjust
>> broken bits that start a line.
>
> Excellent! What an improvement with just a few lines of code!
> Thanks a lot.
Now that the change is in the repository
On Wed, Feb 4, 2015 at 3:43 PM, Werner LEMBERG wrote:
> If it's convenient, have a look at the attached patch/sketch. It
> > adds a property, minimum-length-left-broken, which lets you adjust
> > broken bits that start a line.
>
> Excellent! What an improvement with just a few lines of code! T
>> In case it is easy to implement a `minimum-length-broken' property,
>> please proceed! It would magically improve *a lot* of scores, I
>> guess.
>
> If it's convenient, have a look at the attached patch/sketch. It
> adds a property, minimum-length-left-broken, which lets you adjust
> broken bi
>
>
> On Wed, Feb 4, 2015 at 2:29 PM, David Nalesnik
> wrote:
>>
>>
>> The example file shows how minimum-length and the new property interact
>> with each other.
>>
>>
Will also work with objects other than ties. See attached for slurs,
hairpins, and glissandi.
--David
\version "2.19.16"
\pap
On Wed, Feb 4, 2015 at 2:29 PM, David Nalesnik
wrote:
>
>
> The example file shows how minimum-length and the new property interact
> with each other.
>
>
Attached is an image of the output of the example.
___
lilypond-user mailing list
lilypond-user@gnu
Hi,
On Wed, Feb 4, 2015 at 8:44 AM, Werner LEMBERG wrote:
>
> > Why not make it possible to give different values of minimum-length
> > right when you do the basic override? Perhaps minimum-length could
> > be a pair, one number giving the non-broken value, another giving
> > the broken. Or--l
Hi all,
On Feb 4, 2015, at 9:44 AM, Werner LEMBERG wrote:
> From a philosophical point, however, such a fix basically goes into
> the wrong direction. IMHO, `minimum-length' should do what its name
> advertises, namely controlling the length of the tie, and not the
> distance between its associ
> Why not make it possible to give different values of minimum-length
> right when you do the basic override? Perhaps minimum-length could
> be a pair, one number giving the non-broken value, another giving
> the broken. Or--less intrusive--there could be a property alongside
> it which acted on
On Wed, Feb 4, 2015 at 7:45 AM, David Nalesnik
wrote:
> Hi Werner,
>
> On Wed, Feb 4, 2015 at 12:14 AM, Werner LEMBERG wrote:
>
>
>> > Don't know. In any case, I think the goal should be to make this
>> > work with an override of 'minimum-length, rather than setting
>> > 'minimum-length though
Hi Werner,
On Wed, Feb 4, 2015 at 12:14 AM, Werner LEMBERG wrote:
> > Don't know. In any case, I think the goal should be to make this
> > work with an override of 'minimum-length, rather than setting
> > 'minimum-length though 'after-line-breaking.
>
> The very problem is that minimum-length
> I've found no way to make it work.
OK, thanks for trying.
> Why not tackle the NoteColumn instead?
>
> \version "2.19.15"
>
> \paper {
> indent = 0
> line-width = 50\mm
> ragged-right = #f
> }
>
> {
> c''1 ~ \break
> \once \override Score.NoteColumn.X-offset = 2 %% or
>> However, this has no effect. I guess this is because because the
>> `after-line-breaking' callback is invoked too late in the
>> formatting process.
>
> Yes, it appears that 'minimum-length is consulted before line
> breaking happens, in the callback for ly:spanner::set-spacing-rods
> (in lil
2015-02-03 14:40 GMT+01:00 Werner LEMBERG :
>
> Folks,
>
>
> I'm trying to work around an old problem of broken ties in tightly
> setted music: They can degenerate to a dot, having no horizontal
> extensions anymore. Following the example in section `Difficult
> tweaks' of the notation reference (
Hi Werner,
On Tue, Feb 3, 2015 at 7:40 AM, Werner LEMBERG wrote:
>
> Folks,
>
>
> I'm trying to work around an old problem of broken ties in tightly
> setted music: They can degenerate to a dot, having no horizontal
> extensions anymore. Following the example in section `Difficult
> tweaks' of
> They can degenerate to a dot, having no horizontal extensions
> anymore.
extensions -> extent
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Folks,
I'm trying to work around an old problem of broken ties in tightly
setted music: They can degenerate to a dot, having no horizontal
extensions anymore. Following the example in section `Difficult
tweaks' of the notation reference (with slight changes to change the
property for all siblin
20 matches
Mail list logo
