Re: [Lilypond-auto] Issue 4059 in lilypond: Documentation for issues 3601 (based on 3581), 4042 (NR: "MIDI output", Section 3.5)

[lilypond]

Comment #4 on issue 4059 by address@hidden: Documentation for issues 3601  
(based on 3581), 4042 (NR: "MIDI output", Section 3.5)
http://code.google.com/p/lilypond/issues/detail?id=4059

If midiChannelMapping is incompatible with other features, then  
saying "let's just not document it so that some users may continue using  
it" is not a reasonable option.  For one thing, it establishes a secret  
class of preexisting users who are given access to a feature others  
aren't.  For another, it does not tell anybody the story of what they can  
use when, and when it will fail.

If those features are fundamentally incompatible, then one needs to find a  
scheme or logic how their use could be reconciled in a manner that makes  
enough sense to be documented and explained, and then work on implementing  
this.

In the mean time, the incompatible features still need to be documented on  
their own including the incompatibility so that users at least can make a  
qualified choice.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings