-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with buttons tooltips displayed strings #26198
Comments
For the empty state, I'd agree that saying Probably trivial to fix; for whoever wants to give it a go, search for |
If no one has claimed this issue yet, I would like to take a stab at it :) |
This comment has been minimized.
This comment has been minimized.
Apologies for the delay on this. I am having a difficult time reproing on macOS. I am able to build the app, but the tooltips are not rendering as expected. I am using QT 6.7.3 installed with homebrew. Should I be using a different version? |
You need Qt 6.2.4 for the time being; see https://github.com/musescore/MuseScore/wiki/Install-Qt-and-Qt-Creator. Newer versions indeed cause problems with tooltips. |
There's another instance of this issue in the tool bar: Why does 3 show the strings of 2? In 3 there's no open score, it should show the strings of 1 I'm gonna edit the title. This is not a translation-related issue. |
These are the buttons in question.
Open and run the program empty, hover above the buttons with the mouse: the three tooltips display strings 4068-4070, with the word STAVES.
righi=staves
Then, open a grand staff score, select the only instrument in the panel (Piano) and check again the same tooltips: now, they display strings 4072-4074, with the word INSTRUMENTS.
strumenti=instruments
Expected behaviour: the tooltips always display the same set of strings.
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670
The text was updated successfully, but these errors were encountered: