…entID wind.flutes.whistle.tin

…used in various actions relative to current score state

Qt 5.14 introduces serialisation/deserialisation for enum classes,
this results in ambiguous templates between qdatastream.h and preferences.h.
we specialize everything to workaround this.

+ fix one last problem in #53236

…sposition and pitches messed up

…facts

Most of the MuseScore GUI uses standard Qt widgets and thus is as accessible
as one can reasonably expect - especially now that the palettes have moved to QML.
The main issue thing preventing other screenreaders from being viable is the scoreview.
The accessibility implementation made for the screenreader several years ago
works for NVDA, but a number of small details prevent other screenreaders from working.
This change addresses these, allowing JAWS to work relatively normally,
and Windows Narrator to also work with a manual assist (Narrator + Tab shortcut).
These changes don't adversely affect NVDA, and actually improve its response somewhat,
fixing some of the mysterious "split button" texts that were being read.

The changes here ar small but collectivey they make a difference,
oth in getting JAWS and Narrator to work better out of the box,
but also in making it easier to further script JAWS to provide enhanced accessibility.
I used the Microsot Accessibility Insights tool to find and debug many of these issues.

- added object names and accessible text for the container objects in the main window
- fixed the rect() returned by the scoreview to use global screen coordinates
- gave the AccessibleScoreView a role() of StaticText rather than NoRole
- allow Description as well as Value as keys to access the accessibility text()
- allow Qt to determine the window() for the AccessibleScoreView
- override isValid() to be sure it always returns true

Tese changes allow assistive tools to better associate events with objects,
and objects with windows, which is necessary in order for things to work reliably.
Otherwise, there were cases where the assistive tools would be unable
to find the correct object or window.

Most of the changes should be completely non-controversial and harmless at worst.
The change from NoRole to StaticText yielded best results after trying quite a few options.
This was the only meaningful role read by Windows Narrator at all,
and one of the few recognized as valid and by Accessibility Insights.

There are still cases where the screenreader can get confused about the current/active object,
Sometimes it can be useful to press Alt twice (transfer focus to menu bar and back).
But things seem *much* better with these changes, in my testing.

Align the text on the left and make the size policy of spin box "Expanding".

[Inspector/Regression] fix #299072: style setting for fingering in Inspector has no items

fix build with Qt5.14

fix #298887: generic wind.flutes.whistle.tin is ambiguous

Makes running plugins from menu be visible by a telemetry. Running
plugins via shortcuts still remains untracked.

…ut can work with multiple states

Action filter events

…plugin

…ne, Image

After commit 41e64aa

resolves https://musescore.org/en/node/299545

Fix #299518: Add "Soprano Clef (French, 20th/18th century)"

fix #299545: Incorrect Harmonicas Ranges

[Inspector] Move "Properties" buttons inside inspector panels

Improve Split Staff dialogue

…-transpose-multi-instrument

fix MusicXML export part of #294815 - [Musicxml im-export] - New Tran…

fix #44796: enable ptb import

[Inspector] move Tremolo Bar Properties into Inspector (fix #53236)

…oon-instrument

Support for xaphoon instrument

Fix new Pocket-Saxes

New files bundled in AppImage:

- libcupsprintersupport.so - Qt printsupport plugin
- libnss3.so - a fallback for Chromebook devices
- findlibs - tiny C program to check system libraries

fix #297719: AppImage: add more libraries

Update copyright

…facts

Most of the MuseScore GUI uses standard Qt widgets and thus is as accessible
as one can reasonably expect - especially now that the palettes have moved to QML.
The main issue thing preventing other screenreaders from being viable is the scoreview.
The accessibility implementation made for the screenreader several years ago
works for NVDA, but a number of small details prevent other screenreaders from working.
This change addresses these, allowing JAWS to work relatively normally,
and Windows Narrator to also work with a manual assist (Narrator + Tab shortcut).
These changes don't adversely affect NVDA, and actually improve its response somewhat,
fixing some of the mysterious "split button" texts that were being read.

The changes here ar small but collectivey they make a difference,
oth in getting JAWS and Narrator to work better out of the box,
but also in making it easier to further script JAWS to provide enhanced accessibility.
I used the Microsot Accessibility Insights tool to find and debug many of these issues.

- added object names and accessible text for the container objects in the main window
- fixed the rect() returned by the scoreview to use global screen coordinates
- gave the AccessibleScoreView a role() of StaticText rather than NoRole
- allow Description as well as Value as keys to access the accessibility text()
- allow Qt to determine the window() for the AccessibleScoreView
- override isValid() to be sure it always returns true

Tese changes allow assistive tools to better associate events with objects,
and objects with windows, which is necessary in order for things to work reliably.
Otherwise, there were cases where the assistive tools would be unable
to find the correct object or window.

Most of the changes should be completely non-controversial and harmless at worst.
The change from NoRole to StaticText yielded best results after trying quite a few options.
This was the only meaningful role read by Windows Narrator at all,
and one of the few recognized as valid and by Accessibility Insights.

There are still cases where the screenreader can get confused about the current/active object,
Sometimes it can be useful to press Alt twice (transfer focus to menu bar and back).
But things seem *much* better with these changes, in my testing.

…Sabatella/MuseScore into 299387-generic-screenreader-support