Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]

[Federico Bruni]

Thanks Carl,

yes, the issue is related to relative mode

Il giorno gio, 21/04/2011 alle 07.13 -0600, Carl Sorensen ha scritto:
> 
> put an octave check on the second chord.  That should solve the
> problem.
> 
> <g b e>8 <a='' d fis> 

I made several tries but none worked.
This works:

  \octaveCheck c'
  \chordGlissando
  <bes cis fis>8 <b\3 d g>


(full snippet attached)

Maybe it could be added in the Documentation (NR 2.4.1, Default
tablatures)?

Also, I have a nitpick suggestion: is it possible to make the following
sentence more "visible"? A warning/note maybe?

"String numbers are necessary for TabStaff because automatic string
calculations are different for chords and for single notes, and
\chordGlissando draws lines between single notes."

In the attached snippet you can see that one more bar is added in chord
glissando if string numbers are not indicated.  I think that users
should be warned about this possible error.

Thanks,
Federico

ChordGlissando_consecutive.ly
Description: Text Data