Sorry for the repeat messages. I now have a working version. This is a
callback for InstrumentName.after-line-breaking. It looks at whether the
next Staff below is alive on the current system, and if it's not, displays
the instrumentName for this Staff instead of the shortInstrumentName. This
is a
Making some progress on this. I've managed to figure out how to use
ly:grob-get-vertical-axis-group-index to only look at the current Staff and
the next one below. That's clunkier than finding the VerticalAxisGroups that
belong to the same StaffGroup, but it's a start.
My problem now is finding a
I reviewed the C++ file. I believe others are more qualified to review
the patch as a whole.
https://codereview.appspot.com/321250043/diff/1/lily/chord-name-engraver.cc
File lily/chord-name-engraver.cc (right):
Hi folks
I've made a LilyDev container which can be run with systemd-nspawn.
You can download v0.1 and find the instructions here:
https://github.com/fedelibre/LilyDevOS
This is only for Linux users at the moment.
I'm not sure if you need a certain version of systemd to run it
correctly.
Hi developers,
I’ve just uploaded a patch for review as a part of my Google Summer of Code
project to improve the internal representation of chords. What I’m aiming to do
here is eliminate the ambiguity that comes from naming chords simply based off
the notes. Currently, the information input
