Below you will find pages that utilize the taxonomy term “User experience”
Articles
Interval transposition in MuseScore
Transposition in MuseScore 0.9.5 and earlier makes guesses on the pitch-spelling of the transposed notes and often guesses incorrectly. I created a reference table that can be used for transposing notes without losing the correct pitch spelling. A human transposing notes would use their existing knowledge of scales, plus various other mental tricks. However the method outline below uses a different approach that should be easier to code.
Articles
Mouse interaction in MuseScore
For many users the mouse is the primary means of interacting with MuseScore. This article focuses on the icons in the Note Input toolbar and the Palettes with the goal of optimizing mouse interaction in MuseScore.
Articles
MuseScore: First Impressions
present below my initial impressions and observations during my first few days with MuseScore 0.9.2 (Revision 888) for Windows XP. I wrote down any issues I encountered day-by-day.
Articles
Interface Design in Canorus: Reducing Modes
Due to the complexities of music notation, music software has a tendency to have many modes. Notation software may have a separate mode (tool) for note entry, title text, lyric text, slurs, expressions, accents, etc. Compare this to handwritten notation which uses one tool for all these elements: a pencil. Understandably notation software can be daunting or frustrating for even the seasoned musician or composer. Due to the complexity of music notation and the limitations of the computer interface, it is not possible to achieve an entirely modeless design. Even when composing by hand most people will encounter at least two modes: writing (with pen or pencil) and playback (usually piano).
However, the notation editor Canorus should strive to minimize unnecessary modalism by reducing the number of modes and reducing the barriers between these modes.