gt; grob
> >>> internally calculate its own control points rather than relying on it
> >>> being
> >>> calculated elsewhere (also attached):
> >>
> >> Works great! I improved it further by making it compatible with ties
> too:
> >>
>
ess property and having each grob
>>> internally calculate its own control points rather than relying on it
>>> being
>>> calculated elsewhere (also attached):
>>
>> Works great! I improved it further by making it compatible with ties too:
>>
>>
>>
On Thu 10 Mar 2016 at 10:19:29 (-0600), Cynthia Karl wrote:
> On Thu, 10 Mar 2016 06:04:57 -0700 (MST) tisimst
> schrieb:
> >
> > HTH,
> > Abraham
> >
> > P.S. Some of the power users on this list filter inline images, so if you
> > wouldn't mind making the image an
n relying on it
>> being
>> calculated elsewhere (also attached):
>
> Works great! I improved it further by making it compatible with ties too:
>
>
> #(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob)
> (let* ((cpf (if (grob::has-interface
eat! I improved it further by making it compatible with ties too:
#(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob)
(let* ((cpf (if (grob::has-interface grob 'tie-interface)
ly:tie::calc-control-points
ly:slur::calc-control-points))
alculate its own control points rather than relying on it being
calculated elsewhere (also attached):
\version "2.19.36"
#(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob)
(let* ((cpt (ly:slur::calc-control-points grob))
(cp0 (car cpt))
2016-03-11 10:23 GMT+01:00 Sharon Rosner :
>> This problem arose before.
>> One needs to set 'thickness before-line-breaking, but then you don't
>> have access to the control-points, as far as I remember.
>> I'm not sure there is any way, have to think about it.
>
> Can you
> This problem arose before.
> One needs to set 'thickness before-line-breaking, but then you don't
> have access to the control-points, as far as I remember.
> I'm not sure there is any way, have to think about it.
Can you explain what’s going on? As far as I could tell from debugging the
2016-03-11 10:01 GMT+01:00 Sharon Rosner :
>> Thus again: how should it look, in cases where a broken slur has a
>> (very) long and a (very) short part?
>> Some average-thickness? Or something else?
>
> The problem is not with the broken slurs, but rather with the other slurs
>
16, 17-19, 20-23
etc.
Thanks
Sharon
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188431.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-use
2016-03-11 1:18 GMT+01:00 Sharon Rosner <cico...@gmail.com>:
>> How should it look in situations like below?
>>
>> \score {
>> { c'1( \break d') \repeat unfold 12 { d' \noBreak } c'( \break c' d' c' d') }
>> \layout {
>> \override Slur.after-line-bre
> How should it look in situations like below?
>
> \score {
> { c'1( \break d') \repeat unfold 12 { d' \noBreak } c'( \break c' d' c' d') }
> \layout {
> \override Slur.after-line-breaking = #(variable-slur-thickness 3 10 1.4
> 12.7)
> }
> }
I created something
> Sharon
How should it look in situations like below?
\score {
{ c'1( \break d') \repeat unfold 12 { d' \noBreak } c'( \break c' d' c' d') }
\layout {
\override Slur.after-line-breaking = #(variable-slur-thickness 3 10 1.4 12.7)
}
}
Cheers,
Harm
_
Hi Abraham,
Putting this code into actual use, I found a show stopper. After a line
break, the slur thickness stops being adjusted and reflects the default
thickness value.
Any idea?
Sharon
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness
lsr.di.unimi.it/LSR/Item?id=1028
>> >
>>
>> The header of the third score isn’t correct: Thickness goes from 1.2 to
>> 2.7, not 1.4 to 2.7.
>
>
> (facepalm) Thanks. Corrected.
>
> - Abraham
Hi Abraham,
I had a look.
Pretty nice one, some nitpicks, though.
At 10:56 10/03/2016 -0600, Matthew Skala wrote:
On Thu, 10 Mar 2016, Brian Barker wrote:
At 10:33 10/03/2016 -0600, Matthew Skala wrote:
... HTML in email is usually spam.
You are joking, of course!
No.
OK, I'll rephrase that to help you: either you *have to be* joking or
you are plain
On Thu, 10 Mar 2016, Brian Barker wrote:
> At 10:33 10/03/2016 -0600, Matthew Skala wrote:
> > ... HTML in email is usually spam.
>
> You are joking, of course!
No.
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/
At 10:33 10/03/2016 -0600, Matthew Skala wrote:
... HTML in email is usually spam.
You are joking, of course!
Brian Barker
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
now that some other regular list followers have mentioned this in the
past. Perhaps doing both is how to satisfy both worlds, like you said?
Best,
Abraham
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Inline-images-was-Re-Variable-slur-thickness-tp188389p188391.html
Sent
On Thu, 10 Mar 2016, Cynthia Karl wrote:
> Why on earth would anyone filter inline images?
I filter HTML, because HTML in email is usually spam. "Inline" images
imply HTML and thus get filtered too.
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
achment.html was
> not found on this server.
That’s not very convenient at all. Am I the only one with this problem?
What’s the solution?
Maybe it would be nice if inline images were also added as attachments?
Regards,
Pat Karl
>
> --
> View this message in context:
> ht
correct: Thickness goes from 1.2 to
> 2.7, not 1.4 to 2.7.
>
(facepalm) Thanks. Corrected.
- Abraham
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188388.html
Sent from the User mailing list archive at Nabble.com._
Am 10.03.2016 um 16:56 schrieb tisimst:
Submitted to LSR: http://lsr.di.unimi.it/LSR/Item?id=1028
The header of the third score isn’t correct: Thickness goes from 1.2 to
2.7, not 1.4 to 2.7.
___
lilypond-user mailing list
lilypond-user@gnu.org
e solution:
>>
>> Fantastic! I refactored the code to make it easier to change the
>> parameters:
>>
>
> +1. Nicely refactored.
>
Submitted to LSR: http://lsr.di.unimi.it/LSR/Item?id=1028
- Abraham
--
View this message in context:
http://lilypond.1069038.n5.na
;
+1. Nicely refactored.
- Abraham
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188379.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lil
> I was thinking about this just yesterday. Here's a reasonable solution:
Fantastic! I refactored the code to make it easier to change the parameters:
#(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob)
(let* ((cpt (ly:grob-property grob 'control-points))
(
t. :-)
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188377.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
p://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
28 matches
Mail list logo