musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.3k stars 2.66k forks source link

Dialogue for Export MIDI: Please explain 'RPN' #17399

Open grigorax opened 1 year ago

grigorax commented 1 year ago

Your idea

Problem: In order to understand the 'RPN' option in the MIDI dialogue, I had to search around quite a bit on the web to find an explanation of this term, and even then (see below) I am not much the wiser.

There is scope for the dialogue to be more helpful here, as I suspect many other people won't know either.

The text should read something like "[] Include the RPNs (Registered Parameter Numbers). For advanced users of MIDI."

The reason it would be 'advanced' is clear if we look at the parameters currently registered with the IMA (whatever that is πŸ˜†): 0x0000 – Pitch bend range 0x0001 – Fine tuning 0x0002 – Coarse tuning 0x0003 – Tuning program change 0x0004 – Tuning bank select 0x0005 – Modulation depth range

Whew!

Ref: https://www.recordingblogs.com/wiki/midi-registered-parameter-number-rpn

Proposal. The text should read something like "[] Include the RPNs (Registered Parameter Numbers). For advanced users of MIDI."

Problem to be solved

The user will not be left unsure whether or not they should have ticked this box.

Prior art

No response

Additional context

A related post is: Additional text for MU4 User Manual: File export / File formats / MIDI formatΒ #17400

Jojo-Schmitz commented 1 year ago

A response of @cbjeukendrup to my question on discord on how to do tooltips in QML:


We use a custom tooltip system. See for example how it is used in FlatButton.qml. The relevant code is:

        onContainsMouseChanged: {
            if (!Boolean(root.toolTipTitle)) {
                return
            }

            if (mouseArea.containsMouse) {
                ui.tooltip.show(root, root.toolTipTitle, root.toolTipDescription, root.toolTipShortcut)
            } else {
                ui.tooltip.hide(root)
            }
        }

So the relevant functions are ui.tooltip.show and ui.tooltip.hide. The first argument is the visual item to which the arrow of the tooltip should point.


Note that Mu3 had the same issue...

Issue stems from https://musescore.org/en/node/348727