> I have uploaded a new binary which addresses, to some extent, a couple of your points below.
Yes, much better! I'd call the vertical bounding box issue resolved, no sense worrying about further tweaking of that. > The text typed in by the user is normalized to lower case, but is then compared directly with the list of chord > names read from the xml file. Odd. Is that normalization new with 2.0? This works fine in 1.X using stdchords.xml typing "CMaj7". Anyhow, this will become a non-issue if/when we get the parser happening! But it does raise an issue: to what extent should the parser be cases sensitive? I think it should be completely, and if we wish to allow both Maj and maj to be acceptable abbreviations for major, we'll have to do so explicitly. Otherwise, what do we do for people who wish CM7 to mean major seventh, Cm7 to mean minor seventh? I personally reserve a special place in hell for this, but there's no denying people do it. Marc ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
