Hi Fennel,
> I’d like to adjust the size of certain script marks like trills and bowings
> relative to the staff size. The script class doesn’t seem to let you change
> the symbol’s size.
Of course it does! If you look at the bottom of that page, you’ll see that
Script inherits many interfaces
I’d like to adjust the size of certain script marks like trills and bowings
relative to the staff size. The
[script](https://lilypond.org/doc/v2.25/Documentation/internals/script) class
doesn’t seem to let you change the symbol’s size.
~Fennel
>> Ah, yes, I forgot that it is possible to extend the `props` alist.
>> Thanks a lot!
>
> This is not exactly extending the probs, but passing additional
> parameters in details.
Yep, I answered too quickly and was too lazy to correct myself :-)
> It would be great to generally have a grob pr
er
of overloading things (what if at some point you want to include a property
that later is then introduced as actual grob property?).
I think it does make sense to differentiate more between grob properties and
general properties, and doing something like
\tweak default-properties.foo
would b
Werner LEMBERG writes:
> Hello David,
>
>
>>> is it possible to access markup properties like `baseline-skip` via
>>> \tweak?
>>
>> Have you tried?
>
> Well, yes, but ...
>
>> Check out the following example where I just add a few lines in
>> In the example below, I want to set the markup property `bar` as a
>> tweak to influence `\foo`.
>
> you could of course do something like
>
> %%%
> #(define-markup-command (foo-markup layout props) ()
>#:properties ((bar #f) (details '()))
>
Hello David,
>> is it possible to access markup properties like `baseline-skip` via
>> \tweak?
>
> Have you tried?
Well, yes, but ...
> Check out the following example where I just add a few lines in
> front of what you wrote:
... it didn't occur to me to
Am Donnerstag, 20. Juni 2024, 07:02:48 MESZ schrieb Werner LEMBERG:
> Folks,
>
>
> is it possible to access markup properties like `baseline-skip` via
> \tweak? It is often necessary to define a markup command that gets in
> turn wrapped into a music function, and for such si
Werner LEMBERG writes:
> Folks,
>
>
> is it possible to access markup properties like `baseline-skip` via
> \tweak?
Have you tried?
If it is a grob property...
> In the example below, I want to set the markup property `bar` as a
> tweak to influence `\foo`.
Check out
Folks,
is it possible to access markup properties like `baseline-skip` via
\tweak? It is often necessary to define a markup command that gets in
turn wrapped into a music function, and for such situations a
tweak-like command would be quite handy.
In the example below, I want to set the
*facepalm* - thank you!!
You've mistyped "positions" as "position" (hence the warning “cannot
find the property type-check…”).
--
Diese E-Mail wurde von Avast-Antivirussoftware auf Viren geprüft.
www.avast.com
You've mistyped "positions" as "position" (hence the warning “cannot find the
property type-check…”).
signature.asc
Description: This is a digitally signed message part
Hi Group and Merry Christmas :)
I do not find the right way to tweak the slur position here:
---8<--
\version "2.24.0"
{\relative {\tupletUp \tuplet 3/2 { as'2 b4 } \override Slur.position
=#'(5 . 5) \tuplet 3/2 { c4 (d e) } f\fermata}}
-->8---
I kn
On Wed, Jul 19, 2023 at 3:41 PM Jean Abou Samra wrote:
> \tweak color #(if (equal? DOWN (ly:grob-property grob 'direction)) red
> blue)
>
> You just forgot to wrap the expression in (lambda (grob) ...) .
>
Yes, that's it:
%%% BEGIN %%%
\version "2.25.3"
> \tweak color #(if (equal? DOWN (ly:grob-property grob 'direction)) red
> blue)
You just forgot to wrap the expression in `(lambda (grob) ...)` .
Best,
Jean
signature.asc
Description: This is a digitally signed message part
Hi,
Two examples appear below.
The first works; it uses \override with a callback.
The second doesn't work; it attempts to use \tweak with a callback:
%%% BEGIN %%%
\version "2.25.3"
\markup "Conditionally colors both tuplet brackets:" \markup \vspac
Dear Jean,
A million thanx. That's great it works like a charm.
You made my day!
Best
Karim
On Sun, Jun 25, 2023 at 08:38:18PM +0200, Jean Abou Samra wrote:
> Le vendredi 16 juin 2023 à 15:24 +0200, Jean Abou Samra a écrit :
>
>
> > >
> > I don't have the time to find a solution right now, b
Le vendredi 16 juin 2023 à 15:24 +0200, Jean Abou Samra a écrit :
> >
> I don't have the time to find a solution right now, but for a start, here is
> already a more "M" MWE: [...]
This appears to work better:
```
\version "2.24.1"
#(define (Workaround_engraver context)
(let ((bars '(
Fri, Jun 16, 2023 at 03:24:20PM +0200, Jean Abou Samra wrote:
> Le vendredi 16 juin 2023 à 14:59 +0200, Karim Haddad a écrit :
>
> > I customize staffs using the following tweak:
> > [...]
> >
> > Whenever there is a pagebreak (explicit or automatic), the StaffGroupB
Le vendredi 16 juin 2023 à 14:59 +0200, Karim Haddad a écrit :
> I customize staffs using the following tweak:
> [...]
>
> Whenever there is a pagebreak (explicit or automatic), the StaffGroupBar
> disappears.
> I know i am missing something here.
> Here is a somehow not s
Dear All,
I have this problem:
I customize staffs using the following tweak:
kHide = {\hideNotes
\stopStaff
\override TupletBracket.transparent=##t
\override TupletNumber.transparent=##t
\override Staff.BarLine.transparent=##t
\override
On 30/01/2023 23:08, Ahanu Banerjee wrote:
> Perhaps the documentation could be amended to clarify how neutral direction
> is handled for slurs? There are two documentation pages here that mention
> slur orientation but don't describe the calculation that occurs in
> \slurNeutral:
> https://lily
ra wrote:
>
>> On 30/01/2023 02:20, Ahanu Banerjee wrote:
>> > When I attempt to change the "direction" property of a slur, whether
>> that is with \tweak or \override, I cannot set the direction to neutral
>> (0). UP (1) and DOWN (-1) work fine, but when
>> But the user shouldn't see an assertion error even in case of a wrong
>> argument, right?
>
> Yeah,
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1828
Thanks!
Werner
On 30/01/2023 08:19, Werner LEMBERG wrote:
>
>>> When I attempt to change the "direction" property of a slur,
>>> whether that is with \tweak or \override, I cannot set the
>>> direction to neutral (0). UP (1) and DOWN (-1) work fine, but when
>
o the drul array.
Cheers,
Valentin
Am Montag, 30. Jänner 2023, 08:19:41 CET schrieb Werner LEMBERG:
> >> When I attempt to change the "direction" property of a slur,
> >> whether that is with \tweak or \override, I cannot set the
> >> direction to neutra
>> When I attempt to change the "direction" property of a slur,
>> whether that is with \tweak or \override, I cannot set the
>> direction to neutral (0). UP (1) and DOWN (-1) work fine, but when
>> setting to 0, I get the following error:
>>
>> &quo
Thank you so much!
-Ahanu
On Sun, Jan 29, 2023, 20:36 Jean Abou Samra wrote:
> On 30/01/2023 02:20, Ahanu Banerjee wrote:
> > When I attempt to change the "direction" property of a slur, whether
> that is with \tweak or \override, I cannot set the direction to neutral
On 30/01/2023 02:20, Ahanu Banerjee wrote:
> When I attempt to change the "direction" property of a slur, whether that is
> with \tweak or \override, I cannot set the direction to neutral (0). UP (1)
> and DOWN (-1) work fine, but when setting to 0, I get the following erro
When I attempt to change the "direction" property of a slur, whether that
is with \tweak or \override, I cannot set the direction to neutral (0). UP
(1) and DOWN (-1) work fine, but when setting to 0, I get the following
error:
"Assertion failed: d, file
/home/lily/lilypond
Ahanu Banerjee writes:
> Never mind, it appears that adding "\etc" does what I am trying to do:
>
> makeRed = -\tweak color "red" \etc
Pretty much the primordial use case for \etc .
--
David Kastrup
Never mind, it appears that adding "\etc" does what I am trying to do:
makeRed = -\tweak color "red" \etc
On Sun, Jan 29, 2023 at 5:53 PM Ahanu Banerjee
wrote:
> Thanks for the quick reply. I am looking to create a function that can
> apply to more than one type o
Thanks for the quick reply. I am looking to create a function that can
apply to more than one type of object, in this instance, slurs,
articulations, and possibly fingerings. All the examples I have seen
require specifying the object. Is it possible to have a function behave
like "-\tweak&
On 29/01/2023 23:45, Ahanu Banerjee wrote:
> How can I define a function that applies one or more tweaks to the object
> that comes after it?
>
> example: I want the following expression to be a function called "\makeRed":
> -\tweak color "red"
>
> so
How can I define a function that applies one or more tweaks to the object
that comes after it?
example: I want the following expression to be a function called "\makeRed":
-\tweak color "red"
so that I can type \makeRed \downbow instead of -\tweak color "red" \downbow
Thanks,
-Ahanu
Le 01/11/2022 à 19:59, David Kastrup a écrit :
It makes more sense if
a) a tweak on an to-be-expanded chord (no non-post-event chord elements)
is applied to the ChordEvent expression itself after all.
b) when expanding a RepeatChord, tweaks get copied over to the created
elements.
That adds
Werner LEMBERG writes:
>> [...] As you can deduce from the existence of the \chordRepeats
>> function, the substitution of q is not immediate. In contrast,
>> \tweak takes effect immediately by modifying each of the notes in
>> the chord. Since there are no notes yet
> [...] As you can deduce from the existence of the \chordRepeats
> function, the substitution of q is not immediate. In contrast,
> \tweak takes effect immediately by modifying each of the notes in
> the chord. Since there are no notes yet in the "q" chord at the
&g
Le 31/10/2022 à 16:08, Paul Hodges a écrit :
I wanted to lengthen the stem of a pair of tied chords, but it didn't
work as expected. After some playing around, I found that I cannot
tweak the properties of a chord represented by q (repeating the
previous chord), but that the tweaks o
Oops - start should read:
I wanted to lengthen the stem of only the second of a pair of tied chords.
From: Paul Hodges
To:
Sent: 31/10/2022 15:08
Subject: Curious behaviour of q and a tweak
I wanted to lengthen the stem of a pair of tied chords, but it didn't wo
I wanted to lengthen the stem of a pair of tied chords, but it didn't work as
expected. After some playing around, I found that I cannot tweak the
properties of a chord represented by q (repeating the previous chord), but that
the tweaks on the original chord get carried over. This ex
Thanks to you and Jean Abou Samra. I have been able to do all the things I
needed (including some not mentioned) using what I have [re-]learned today.
Paul
From: Xavier Scheuer
To: Paul Hodges
Cc: lilypond-user
Sent: 11/04/2022 12:12
Subject: Re: How to tweak dot sizes
staccato, in proportion of course), and finding the tweak
for this has defeated me. I wonder if it's the "Y-extent" property - but
this doesn't feel right; I'd expect something like "size", but that doesn't
seem to be available for dots.
>
> Can som
n proportion of course), and finding the
tweak for this has defeated me. I wonder if it's the "Y-extent"
property - but this doesn't feel right; I'd expect something like
"size", but that doesn't seem to be available for dots.
Can some kind soul p
have modified \tempo
output simply by using markup, and I have found I can thicken hairpin lines
slightly using the "thickness" property.
However, I'd also like to slightly increase the size of dots (both augmentation
and staccato, in proportion of course), and finding the twe
Le 21/12/2021 à 22:29, David Kastrup a écrit :
Jean Abou Samra writes:
[Valentin]
Hello Jean, hello David, hello Kieren,
you should even be able to write (if sten (ly:stencil-extent sten)),
as the stencil should always be a stencil or #f.
The two universally accepted values for any prop
Jean Abou Samra writes:
> [Valentin]
>> Hello Jean, hello David, hello Kieren,
>>
>> you should even be able to write (if sten (ly:stencil-extent sten)),
>> as the stencil should always be a stencil or #f.
>
>
> The two universally accepted values for any property
> regardless of the predicate ar
Le 21/12/2021 à 21:49, David Kastrup a écrit :
Your "if" has no else path. Maybe replace it with "and", assuming that
ChordName knows how to deal with an X-offset of #f (which tends to be a
valid setting for any predicate in grob properties).
Ouch. Looking at the relevant code path uncovered
Hello David,
using and here is a fancy way of doing things, that is true. Best way would
probably to use a suitable else value like '(0 . 0) or something, I guess.
Cheers,
Valentin
21.12.2021 21:58:59 David Kastrup :
> Valentin Petzel writes:
>
>> Hello Jean, hello David, hello Kieren,
>>
>
Valentin Petzel writes:
> Hello Jean, hello David, hello Kieren,
>
> you should even be able to write (if sten (ly:stencil-extent sten)),
> as the stencil should always be a stencil or #f.
The return value will still be neither #f nor a dimension unless you
replace "if" with "and".
--
David Ka
Hello Jean, hello David, hello Kieren,
you should even be able to write (if sten (ly:stencil-extent sten)), as the
stencil should always be a stencil or #f.
Cheers,
Valentin
21.12.2021 21:42:13 Jean Abou Samra :
> Le 21/12/2021 à 21:33, David Kastrup a écrit :
>> Kieren MacMillan writes:
>>>
Jean Abou Samra writes:
> Certainly. Kieren, try this:
>
> \version "2.22.1"
>
> \layout { ragged-right = ##f }
>
> music = \chordmode {
> c1 c:7 c:m7 c':m6.4.2/ees \once \omit ChordName c
> }
>
> \score {
> <<
> \new ChordNames \music
> \new Staff \music
> >>
> \layout {
> \c
Hi all,
>>> Any thoughts about what might be going wrong?
>> It is applied to a grob that has been given the \omit treatment?
> Certainly. Kieren, try this
Perfection!
Thank you, Aaron and David and Jean!
Onward and upward. =)
Kieren
Le 21/12/2021 à 21:33, David Kastrup a écrit :
Kieren MacMillan writes:
Hi again,
When I try to use it in my main file, I get this:
In procedure ly:stencil-extent in expression (ly:stencil-extent sten X):
/Users/kmac/Documents/01_music/scores/_include/paper/musical.ily:254:21:
Wrong type ar
Kieren MacMillan writes:
> Hi again,
>
> When I try to use it in my main file, I get this:
>
> In procedure ly:stencil-extent in expression (ly:stencil-extent sten X):
> /Users/kmac/Documents/01_music/scores/_include/paper/musical.ily:254:21:
> Wrong type argument in position 1 (expecting Stenci
Hi again,
When I try to use it in my main file, I get this:
In procedure ly:stencil-extent in expression (ly:stencil-extent sten X):
/Users/kmac/Documents/01_music/scores/_include/paper/musical.ily:254:21: Wrong
type argument in position 1 (expecting Stencil): #f
Any thoughts about what might
Hi Aaron,
> I've used something like this in the past
That's great! I just wrapped your 'center-er' in a (max -2 etc), and it's
exactly what I want:
\version "2.22.0"
\layout { ragged-right = ##f }
music = \chordmode {
c1 c:7 c:m7 c':m6.4.2/ees
}
\score {
<<
\new ChordNames \mus
On 2021-12-21 10:30 am, Kieren MacMillan wrote:
and am once again in need this ChordName alignment feature. Is anyone
out there able to shepherd me through building a callback to make this
happen?
I've used something like this in the past:
\version "2.22.0"
music = \chordmode {
\overri
using friends are downright angry when they see how
quickly I can generate scores and especially parts-from-a-score (those being
almost entirely tweak-free, thanks to my stylesheets!). =)
> On Dec 21, 2021, at 1:30 PM, Kieren MacMillan
> wrote:
>
> Hi all,
>
> I'm crammin
Hi all,
I'm cramming out scores for an upcoming workshop of a new musical**, and am
once again in need this ChordName alignment feature. Is anyone out there able
to shepherd me through building a callback to make this happen?
Thanks,
Kieren.
> On Jun 16, 2018, at 1:41 PM, Kieren MacMillan
>
Hi Werner,
> In case there isn't a nifty trick
You mean *other* than using the [incredible] edition-engraver…? ;)
Cheers,
Kieren.
Hello Werner,
Tag adds a property to music events, as does tweak. So there is no tweak event
that could be tagged. But what would be possible is to write a music function
that removes tweaks from a even if it is (or is not) tagged with some tag.
Cheers,
Valentin
Am Freitag, 26. November 2021
Le 26/11/2021 à 19:21, Werner LEMBERG a écrit :
This time a syntax question: Is it possible to combine `\tag` with
`\tweak`? I have tried the following:
g-\tag #'score \tweak X-offset #-3
_\markup { "foo" } |
However, this makes the `\markup` disappear i
This time a syntax question: Is it possible to combine `\tag` with
`\tweak`? I have tried the following:
g-\tag #'score \tweak X-offset #-3
_\markup { "foo" } |
However, this makes the `\markup` disappear if `\keepWithTag` doesn't
contain `#'score`
Am Mi., 14. Apr. 2021 um 11:48 Uhr schrieb Thomas Morley
:
>
> Am Mi., 14. Apr. 2021 um 10:30 Uhr schrieb Jean Abou Samra
> :
> >
> >
> > Le 13/04/2021 à 23:18, Thomas Morley a écrit :
> >
> > Hi,
> >
> > let's say I've a chord with F
Am Mi., 14. Apr. 2021 um 11:48 Uhr schrieb Thomas Morley
:
>
> Am Mi., 14. Apr. 2021 um 10:30 Uhr schrieb Jean Abou Samra
> :
> >
> >
> > Le 13/04/2021 à 23:18, Thomas Morley a écrit :
> >
> > Hi,
> >
> > let's say I've a chord with F
Am Mi., 14. Apr. 2021 um 11:47 Uhr schrieb Jean Abou Samra :
>
>
> Le 14/04/2021 à 10:30, Jean Abou Samra a écrit :
> >
> >
> > For Y-offset, I haven't found a workaround yet.
> >
>
> Okay, this does the job:
>
> \version "2.22.0"
>
> {
>\set fingeringOrientations = #'(left)
>\once \overrid
Am Mi., 14. Apr. 2021 um 10:30 Uhr schrieb Jean Abou Samra :
>
>
> Le 13/04/2021 à 23:18, Thomas Morley a écrit :
>
> Hi,
>
> let's say I've a chord with Fingerings left.
> Now I want to tweak a certain Fingering a little bit up/down and left/right.
>
>
Le 14/04/2021 à 10:30, Jean Abou Samra a écrit :
For Y-offset, I haven't found a workaround yet.
Okay, this does the job:
\version "2.22.0"
{
\set fingeringOrientations = #'(left)
\once \override Staff.FingeringColumn.positioning-done =
#(lambda (grob)
(let* ((fingering-ar
Am Mi., 14. Apr. 2021 um 10:42 Uhr schrieb Xavier Scheuer :
>
> On Wed, 14 Apr 2021 at 10:31, Jean Abou Samra wrote:
> >
> >
> > Hi,
> >
> > Something very weird seems to be going
> > on. Try:
>
> Hello,
>
> Speaking of weird, the tweaks work if there is only one fingering in the
> chord.
>
> \se
On Wed, 14 Apr 2021 at 10:31, Jean Abou Samra wrote:
>
>
> Hi,
>
> Something very weird seems to be going
> on. Try:
Hello,
Speaking of weird, the tweaks work if there is only one fingering in the
chord.
\set fingeringOrientations = #'(left)
Cheers,
Xavier
--
Xavier Scheuer
Le 13/04/2021 à 23:18, Thomas Morley a écrit :
Hi,
let's say I've a chord with Fingerings left.
Now I want to tweak a certain Fingering a little bit up/down and left/right.
How to do so?
Here a minimal to play with:
{
\set fingeringOrientations = #'(left)
%% belo
Hi,
let's say I've a chord with Fingerings left.
Now I want to tweak a certain Fingering a little bit up/down and left/right.
How to do so?
Here a minimal to play with:
{
\set fingeringOrientations = #'(left)
%% below does not work
\once \override Fingering.Y-offs
> Oops, and of course #etc (or whatever it is called now).
I now have
% A tweak-like function to move dynamics.
moveDyn =
#(define-event-function (x y event) (number? number? ly:event?)
#{ \tweak DynamicLineSpanner.outside-staff-priority ##f
\offset DynamicText.X-offset
Werner LEMBERG writes:
>>> Thanks! Please check whether
>>>
>>> moveDyn =
>>> #(define-event-function (X Y etc) (number? number? ly:music?)
>>> #{ \tweak DynamicLineSpanner.outside-staff-priority ##f
>>>
>> Thanks! Please check whether
>>
>> moveDyn =
>> #(define-event-function (X Y etc) (number? number? ly:music?)
>> #{ \tweak DynamicLineSpanner.outside-staff-priority ##f
>> \tweak DynamicText.X-offset #X
>> \offset Dyna
Werner LEMBERG writes:
>>> moveDynTweak =
>>> #(define-music-function (X Y) (number? number?)
>>> #{ \tweak DynamicLineSpanner.outside-staff-priority ##f
>>> \tweak DynamicText.X-offset #X
>>> \offset Dyn
>> moveDynTweak =
>> #(define-music-function (X Y) (number? number?)
>> #{ \tweak DynamicLineSpanner.outside-staff-priority ##f
>> \tweak DynamicText.X-offset #X
>> \offset DynamicLineSpanner.Y-offset #Y
>> \etc #}
er.outside-staff-priority = ##f
>>> \once \override DynamicText.X-offset = #X
>>> \once \offset Y-offset #Y DynamicLineSpanner
>>> \etc #})
>>>
>>> but this doesn't work.
>>
>> There is a difference between a tweak and an
micText.X-offset = #X
>> \once \offset Y-offset #Y DynamicLineSpanner
>> \etc #})
>>
>> but this doesn't work.
>
> There is a difference between a tweak and an override.
Ah, bad editing, sorry. I tried of course
moveDynT
ffset = #X
> \once \offset Y-offset #Y DynamicLineSpanner #})
>
> {
> g'2
> \moveDyn #-1 #5
> g'\f
> }
>
> How can I convert `\moveDyn' to a \tweak-like function so that I can
> say
>
> g'\moveDynTweak #-1 #5 -\f
>
&
unction (X Y) (number? number?)
> #{ \once \override DynamicLineSpanner.outside-staff-priority = ##f
> \once \override DynamicText.X-offset = #X
> \once \offset Y-offset #Y DynamicLineSpanner #})
>
> {
>g'2
>\moveDyn #-1 #5
>g'\f
> }
>
>H
#})
{
g'2
\moveDyn #-1 #5
g'\f
}
How can I convert `\moveDyn' to a \tweak-like function so that I can
say
g'\moveDynTweak #-1 #5 -\f
instead? I naïvely tried
moveDynTweak =
#(define-music-function (X Y) (number? number?)
#{ \once \override Dynami
@ Brian, I meant:
\version "2.19"
{
a1\sustainOn a -\tweak color #red \sustainOff \sustainOn
}
{
a1
-\tweak bound-details
#`((left . ((Y . 0)
(attach-dir . -2)
(text . ,(markup #:musicglyph "pedal.Ped"
Pierre Perol-Schneider writes:
> Hi,
> What's wrong with this tweak ?
>
> \version "2.19.83"
> {
> a1\sustainOn a-\tweak color #red \sustainOff \sustainOn
> }
The off-on sequence creates only a single grob, and that one is created
by \sustainOn . You can
> On 3 Jun 2019, at 13:14, Pierre Perol-Schneider
> wrote:
>
> Hi,
> What's wrong with this tweak ?
>
> \version "2.19.83"
> {
> a1\sustainOn a-\tweak color #red \sustainOff \sustainOn
> }
>
> TIA
> Cheers,
> Pierre
> ___
Hi,
What's wrong with this tweak ?
\version "2.19.83"
{
a1\sustainOn a-\tweak color #red \sustainOff \sustainOn
}
TIA
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
dtsmarin writes:
> I thought my code didn't work but it looks like it does. Sorry for the
> unnecessary replies.
> Use case:
> Chromatic enharmonic tied notes where normally Lilypond wouldn't work
> correctly. (Ties don't show up if you don't use this hack).
They don't?
\version "2.19.16"
{
I thought my code didn't work but it looks like it does. Sorry for the
unnecessary replies.
Use case:
Chromatic enharmonic tied notes where normally Lilypond wouldn't work
correctly. (Ties don't show up if you don't use this hack).
The problem is that my half-solution ruins the spacing.
#(define e
On 2019-05-01 11:17 am, dtsmarin wrote:
This was an example to show what I'm after.
I need to *change* the stencil (e.g. flat to be sharp ) not the colour
etc.
I know how to change stencil for a single accidental with \override but
\tweak Accidental.stencil doesn't work.
Hmm... \
David Kastrup writes:
> dtsmarin writes:
>
>> Oops! Wrong minimal example!
>>
>>
>> #(define enh-acc
>> (lambda (grob)
>> (let* ((stencil (ly:accidental-interface::print grob))
>>(new-stil
>> (grob-interpret-markup grob
>>(markup
>>
dtsmarin writes:
> Oops! Wrong minimal example!
>
>
> #(define enh-acc
> (lambda (grob)
> (let* ((stencil (ly:accidental-interface::print grob))
>(new-stil
> (grob-interpret-markup grob
>(markup
> #:hspace 1
>
Oops! Wrong minimal example!
#(define enh-acc
(lambda (grob)
(let* ((stencil (ly:accidental-interface::print grob))
(new-stil
(grob-interpret-markup grob
(markup
#:hspace 1
#:musicglyph "accidentals.flat"
dtsmarin writes:
> This was an example to show what I'm after.
> I need to *change* the stencil (e.g. flat to be sharp ) not the colour etc.
> I know how to change stencil for a single accidental with \override but
> \tweak Accidental.stencil doesn't work.
Minimal
This was an example to show what I'm after.
I need to *change* the stencil (e.g. flat to be sharp ) not the colour etc.
I know how to change stencil for a single accidental with \override but
\tweak Accidental.stencil doesn't work.
The closest I've got is this:
#(define rhomb-acc
dtsmarin writes:
> Is it possible to tweak the stencil for an accidental within a chord?
>
> Something similar in functionality with:
> \tweak Stem.color #red
> \tweak Beam.color #green c8 e
> 4
Uh, what is wrong with exactly that?
Is it possible to tweak the stencil for an accidental within a chord?
Something similar in functionality with:
\tweak Stem.color #red
\tweak Beam.color #green c8 e
4
--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
___
lilypond
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Urs,
Many thanks. You seem to have cut the knot I had.
Am Di den 29. Jan 2019 um 12:58 schrieb Urs Liska:
> \set changes a property of a *context*, for example the Voice or the Staff
> while \override changes the property of an object (grob) lik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am Di den 29. Jan 2019 um 12:34 schrieb Pierre Perol-Schneider:
> See also:
> http://lilypond.org/doc/v2.19/Documentation/notation/set-versus-override.html
That is exactly what makes my understanding problems.
It describes something about the
type created within some context.
\tweak changes properties of grobs created by a given music
expression (the association is the same that is being used for
point-and-click on a graphical object leading to a source expression).
--
David Kastrup
___
lilypond-
1 - 100 of 317 matches
Mail list logo
