Re: [Denemo-devel] Articulations

[Richard Shann]

On Sat, 2011-12-10 at 19:28 +0100, Jeremiah Benham wrote:
> Sorry for the top posting... I noticed Nils had this function defined in 
> denemo-modules/selection.scm
> SingleAndTaggedSelectionSwitcher this applies to the single object or all 
> objects under selection.
> 
> So in the file AccentSelectionSwitcher he has:
> (SingleAndSelectionSwitcher d-ToggleAccent)
> 
> This applies to every note in the selection. I think d-ToggleAccent is a 
> built-in though. I am sure it can be replaced. Is this what the menu items 
> should contain (of course replace d-ToggleAccent with the new scripts 
> procedures?). The script procedure would probably best be defined in the same 
> file perhaps.
> 
> I am not sure how the denemo-modules work. In my local git (I have not pushed 
> it yet), I created a file denemo-modules/fonts.scm. It contins:
> ;;; Emmentaler rests
> (define REST0 "")
> (define REST1 "")
> 
> (define REST2 "")
> (define REST3 "")
> (define REST4 "")
> (define REST5 "")
> (define REST6 "")
> (define REST7 "")
> 
> (define Rest0  (string-append "\n" REST0 "\nemmentaler"))
> ............
> 
> I cut these out of denemo.scm. Is this correct. Do these modules get sourced 
> on startup or do they have to be specifically loaded like this:
> (load-from-path "fonts.scm)
The module load commands are all at the top of denemo.scm, you have to
explicitly load them. However, since it has turned out that we don't
need to define names for the emmentaler glyphs in general, we can leave
this for now. OTOH If the glyphs are going to move to different utf8
values or if the font is going to change it could be good to define
things like
(define DENEMO_MARCATO "\n\nemmentaler\n26")
in your new module
and then make the scripts do
(d-DirectivePut-chord-graphic "Marcato" DENEMO_MARCATO)

That's the wrong glyph for Marcato but you will know what I mean.

Richard



> 
> Jeremiah
> 
> 
> On Sat 10/12/11  5:35 AM , Richard Shann  wrote::
> 
> OK, I have checked in d-Marcato
> I think it could be improved before we start cloning it for every sort
> of articulation (and indeed all the other sorts of marks, both
> stem-direction sensitive and not, ie DENEMO_ALT_OVERRIDE and not)
> One thing is to test Marcato::params which is set #f unless called from
> a script - this way a script can force Marcato rather than just toggle
> it.
> And the body of this example could be a utility function placed
> somewhere in denemo-modules - perhaps Nils already has this done?
> 
> Any other improvements????
> 
> 
> NOTE: there is a long-standing bug with the display not expanding when
> you add things too high to be seen. So applying d-Marcato to the top
> staff on a stem-down note will result in the marcato being off screen at
> the top. Time to fix this.
> 
> Richard
> 
> 
> On Sat, 2011-12-10 at 11:25 +0000, Richard Shann wrote:
> > Well, it turns out that d-DirectivePut-chord-graphic is not limited to a
> > single char, it will output a string using the given font and size.
> > 
> > (d-DirectivePut-chord-graphic "test" "
> >   
> > emmentaler
> > 26")
> > puts two U+E190 below the chord. 
> > *And* it turns out that we may need to look at the feta/emmentaler/...
> > story, if I replace emmentaler here with feta then I don't get a
> > character showing, so presumably they have moved the character positions
> > (?).
> > The good news is that we can create the upside down glyphs using cairo -
> > so we don't have to give the two versions of the glyph to Denemo.
> > I'll check in the support for this shortly.
> > 
> > Richard
> > 
> > 
> > On Sat, 2011-12-10 at 10:11 +0000, Richard Shann wrote:
> > > I've had a look, and what I wrote first was right, it is the *graphic*
> > > not the display field that you can use to display any single char from
> > > any font at any size.
> > > There is no up/down support, and there is also reversal support to go in
> > > there, we are essentially talking about switching the graphic glyph
> > > depending on stem up/down and positioning it differently also. I am sure
> > > we have enough capacity in the structure to do this, but I will need to
> > > give it some thought. And then implement the support for it.
> > > 
> > > Richard
> > > 
> > > 
> > > 
> > > > Sorry
> > > > This bit is muddled:
> > > > > These glyphs *are* the image to show in the draw area. You write
> > > > > (d-DirectivePut-note-graphic tag "
> > > > > \xEE\x85\xAD
> > > > > Feta26
> > > > > 24")
> > > > > 
> > > > > and it uses that glyph from that font at 24 point. There are quite a
> > > > few
> > > > > examples of this. We don't need them for any other purpose - issue
> > > > the
> > > > > LilyPond syntax /staccatissimo or whatever it is, and LilyPond
> > > > prints
> > > > it is d-DirectivePut-note-display that can place any string from any
> > > > font at any size.
> > > > I had it in mind to do something for the graphic field, but I am not
> > > > sure how far I got when I was last working on this. It would be better
> > > > if I looked into it and came up with an example.
> > > > 
> > > > Richard
> > > 
> > > 
> > > On Sat, 2011-12-10 at 09:46 +0000, Richard Shann wrote:
> > > > Sorry
> > > > This bit is muddled:
> > > > > These glyphs *are* the image to show in the draw area. You write
> > > > > (d-DirectivePut-note-graphic tag "
> > > > > \xEE\x85\xAD
> > > > > Feta26
> > > > > 24")
> > > > > 
> > > > > and it uses that glyph from that font at 24 point. There are quite a
> > > > few
> > > > > examples of this. We don't need them for any other purpose - issue
> > > > the
> > > > > LilyPond syntax /staccatissimo or whatever it is, and LilyPond
> > > > prints
> > > > it is d-DirectivePut-note-display that can place any string from any
> > > > font at any size.
> > > > I had it in mind to do something for the graphic field, but I am not
> > > > sure how far I got when I was last working on this. It would be better
> > > > if I looked into it and came up with an example.
> > > > 
> > > > Richard 
> > 
> 
> 
> 
> 
>