Add partial loop playback (In/Out position)
Add partial loop playback (In/Out position)
Add partial loop playback (In/Out position)
Add partial loop playback (In/Out position)
Add loop playback feature using events
Removed unneeded include file
fix display of dynamics on mac
honor placement for staccato&tenuto
fix mac build
bagpipe palette updates
Merge pull request #442 from lvinken/13108-bagpipe-palette

bagpipe palette updates
better name for elements array in Note for plugins
better naming for horizontal beam style
Fix part name when changing instrument
Fix #22235 : some ledger lines are too wide in chords with seconds.

If a chord contains an interval of a second (i.e. with flipped note heads) but the flipped note head(s) require no ledger lines, lines wide as the entire chords are generated.

Fixed by constructing ledger lines in two passes each from the 'outside' of the chord toward the staff, once for lines below and once for lines above the staff

See http://musescore.org/en/node/22235 for details and a sample. The commit should fix both issues in the post

NOTE: I had to remove the 'experimental' feature to avoid collision between ledger lines and accidentals: the relevant test is there, but what to do in this case is much more complex than before.
Merge pull request #444 from vgstef/PartNameInstrument

Fix part name when changing instrument
Merge pull request #440 from vgstef/loopPlayback

Add partial loop playback feature (In/Out position) using events
Merge pull request #443 from mgavioli/Fix_22235_ledger_lines_chords_with_seconds

Fix #22235 : some ledger lines are too wide in chords with seconds.
When a score is saved and reloaded, jumps loose any custom text style and markers loose any custom text style and text.

This is because Jump::read() and Marker::read() reset values read from the score with default values.

Fixed by commenting out / deleting those resets.
Re-factor presets and staff types.

1) Built-in staff types have been removed.

2) Presets are internally used as source for the staff types of a new score, to match data in Instruments.xml and as reference to check for modifications.

3) Each new score is given by default one staff type for each preset with the same name.

4) The Instrument page of the New Score Wizard lists (under the name of "Staff types") the default staff types applicable to the instrument (actually it lists the preset, as the score does not have any staff type yet).

5) The "Add | Instruments" dlg box lists all the staff types applicable to the instrument: = to the list of 4) + any user-created staff type.

6) The Staff Properties dlg box lists all the staff types applicable to the instrument: = list in 5)

7) The Staff Type Editor lists all the staff types

This should ensure consistency among the several lists of staff types and avoid duplication of similar items

Terminology:

7) A new staff type created in the editor is named by default with the group name ("Standard-", "Perc-", "Tab-") + the index of the new type in its group + the suffix "[*]" marking a user customisation. The user is anyway able to rename it, if he want.

8) The pitched staff type has been renamed everywhere (hopefully!) to "Standard"

9) The term 'preset' have been removed from the UI, except from the Staff Type Editor where it keeps its meaning of ready-made collections of parameters

The commit affects many files, but a fair number of them have only changes in names of literals. The files with significant code changes are:
libmscore/score.cpp
libmscore/stafftype.cpp/.h
mscore/editstafftype.cpp (code for naming a new staff type)
mscore/instrdialog.cpp (building type list)

Note: as score files store staff type indications as integer indices and the number and order of new default staff types is different from the old built-in types, there is a compatibility issue with old 2.0 score which use percussion and tab staves. In Score::read() (libmscore/scorefile.cpp), there is a rudimentary attempt to cope with this.Old scores will need manual fix anyway. There should not be any (new) compatibility issue with 1.x scores, as they did not use staff types.