Re: glissandi control

[Richard Shann]

On Thu, 2023-09-07 at 09:31 -0700, Donald J. Stewart wrote:
> Thanks Richard! 
> 
> Now I need to correctly add a button. My first attempt was a failure
> which was 
> compounded when I deleted

I may be wrong, but I don't think you can *delete* palettes, they are
just not showing. You should be able to resurrect them with a command
e.g.

Command: Select a Palette to Show
Offers the available palettes to un-hide.
Location: Main Menu ▶ View ▶ Palettes
Internal Name: ChoosePalette

and other in that menu
HTH
Richard


>  all palettes.
> 
> On Thursday, September 7, 2023 12:55:22 AM PDT Richard Shann wrote:
> > On Wed, 2023-09-06 at 16:15 -0700, Donald J. Stewart wrote:
> > > I have inserted the proper command in Lilypond using Frescobaldi,
> > > which is:
> > > 
> > > glissandoSkipOn = {
> > >   \override NoteColumn.glissando-skip = ##t
> > >   \hide NoteHead
> > >   \override NoteHead.no-ledgers = ##t
> > > }
> > > 
> > > glissandoSkipOff = {
> > >   \revert NoteColumn.glissando-skip
> > >   \undo \hide NoteHead
> > >   \revert NoteHead.no-ledgers
> > > }
> > > Is it possible to input this in Denemo?
> > 
> > Yes, you use the command:
> > 
> > Command: LilyPond Definition
> > Create a definition at the head of the LilyPond output. This can
> > then
> > be referenced in the music. See LilyPond documentation.
> > Location: Object Menu ▶ Score
> > Internal Name: LilyPondDefinition
> > 
> > to define the two variables glissandoSkipOn/Off
> > then in the music use
> > 
> > Command: Insert Lilypond
> > Insert or edit a directive in the LilyPond music typesetting
> > language.
> > This can be used for extra spacing, transposing or almost anything.
> > See
> > LilyPond documentation for ideas.
> > Location: Object Menu ▶ Directives
> > Internal Name: InsertStandaloneDirective
> > 
> > to insert \glissandoSkipOn/Off as needed. You can create buttons or
> > menu commands to invoke these as usual.
> > 
> > HTH
> > 
> > Richard
> > 
> > >  My guess is this should be somewhere in the Score block.
> > > 
> > > On Friday, September 1, 2023 12:38:41 AM PDT Richard Shann wrote:
> > > > On Thu, 2023-08-31 at 09:51 -0700, Donald J. Stewart wrote:
> > > > > I would like to control the glissandi as they should point
> > > > > from
> > > > > one
> > > > > note
> > > > > directly to another.
> > > > 
> > > > Well, that is what the command
> > > > 
> > > > Command: Glissando
> > > > Inserts a glissando (portamento, slide), a line joining the
> > > > notehead of
> > > > this and the next note. You may need to displace the following
> > > > note
> > > > horizontally to make the gliss marking visible enough.
> > > > Location: Object Menu ▶ Notes/Rests ▶ Markings ▶ Text/Symbol
> > > > Internal Name: Glissando
> > > > 
> > > > does, I notice it also does the simplest sort of glissando for
> > > > chords.
> > > > For more complex cases (e.g. chords with crossing gliss) you
> > > > will
> > > > need
> > > > to insert the needed LilyPond syntax described at:
> > > > 
> > > > https://lilypond.org/doc/v2.24/Documentation/notation/expressive-marks-a
> > > > s-li nes#index-glissando-1
> > > > 
> > > > which you can do in the LilyPond view (or using Directives-
> > > > >Insert
> > > > LilyPond).
> > > > 
> > > > Once you have found the right syntax to insert for some
> > > > particular
> > > > use,
> > > > you could create a command or palette button to insert it or
> > > > publish it
> > > > on this list so I can take care of that.
> > > > 
> > > > HTH
> > > > Richard
> > > > 
> > > > > I would also like to extend the glissandi across multiple
> > > > > notes,
> > > > > if
> > > > > possible.
> > > > > 
> > > > > 
> > > > > _____________________________________________
> > > > > D o    n a    l    d    J     S  t   e     w    a   r       
> > > > > t
> > > > >            s     o    u   n      d        -          X
> 
> 
> 
>