musescore / musescore/MuseScore
Reload Plugins doesn't work as expected
Open
Nobody has claimed this yet.
community
P3
plugins
regression MS4
UX/interaction
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
- Create a plugin that shows a dialog with a particular message
- Enable it
- Open a score, and use the plugin
- Modify the qml file of the plugin to change the plugin's title/version/text displayed etc.
- Reload plugins, verify the title/version is correct
- Close & re-open the score, and use the plugin again
- Old text is shown.
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.7.3
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Windows 11
Additional context
The only thing that seems to work is restarting MuseScore4.exe. Not even disabling/re-enabling works.
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. Start by reproducing the seven-step case on Windows 11 with a QML plugin, changing its displayed text or metadata and using Reload plugins before reopening the score. Done means the reopened score uses the updated plugin text without restarting MuseScore4.exe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100