Re: Staff.instr code change?

[Erik Sandberg]

On Friday 09 June 2006 15:57, Kieren MacMillan wrote:
> Hi, Han-Wen:
> > Probably the best way is to modify instrument-name-engraver.cc to
> > start a
> > new InstrumentName if the instr property changed from a previous
> > value.
>
> Sounds pretty easy... to mess up if you don't know C++...  ;-)
>

Once I get gub working so I can test&commit my contributions, there will be a 
new hook which makes it possible to passively listen for changes to 
properties.

-- 
Erik