If you implement the change of instrument name ⇒ music property ⇒ instrument
Music is, but will be the score of the specified instrument
The code is still in the pre-change code.
When the previous version was not a problem.
2.0 is from becoming version.
Wishes act accordingly.
unfortunately that translation doesn't make much sense to me, mind to write it up yourself in English?
Indeed in 2.0 this method of changing the instrument doesn't work anymore, instead do a right-rlick into the the staff and select staff properties, there you can change the instrument. Also the instrument name (long, short) and a couple more things.
Closed due to inability to reproduce. Please report, in English, and with precise steps to reproduce, in a new thread if this still troubles you in the latest version (3.4.2).
Comments
Google translate:
If you implement the change of instrument name ⇒ music property ⇒ instrument
Music is, but will be the score of the specified instrument
The code is still in the pre-change code.
When the previous version was not a problem.
2.0 is from becoming version.
Wishes act accordingly.
unfortunately that translation doesn't make much sense to me, mind to write it up yourself in English?
楽器の名前⇒譜面プロパティ⇒楽器の変更を実施すると
If I do "Name of the Instrument -> Staff Properties -> Change Instruments"
譜面は、指定した楽器の譜面になりますが
The staff will be the one according to the instrument I specified.
コードは、変更前のコードのままです。
But the chords will stay the same.
前のバージョンの時は問題ありませんでした。
This bug doesn't occur in previous versions.
2.0バージョンになってからです。
This occurs since 2.0
善処ねがいます。
Regards
Indeed in 2.0 this method of changing the instrument doesn't work anymore, instead do a right-rlick into the the staff and select staff properties, there you can change the instrument. Also the instrument name (long, short) and a couple more things.
Not sure but it could be the same than #62341: Chord symbols don't transpose when changing instrument/transposition in staff properties too. If it's the case, it will be fixed in 2.0.3.
Apparently I was wrong, it works that way in 2.0 too.
Probably lasconic's guess as to what the problem is is better?
Closed due to inability to reproduce. Please report, in English, and with precise steps to reproduce, in a new thread if this still troubles you in the latest version (3.4.2).