Skip to content

Conversation

@miiizen
Copy link
Contributor

@miiizen miiizen commented May 19, 2025

Resolves: #27944

@miiizen miiizen requested review from a user and mike-spa May 19, 2025 07:35
@miiizen miiizen force-pushed the 27944-slash-save branch from 62db5f9 to 2c943f2 Compare May 19, 2025 09:47
write(item->hook(), xml, ctx);
}
if (item->showStemSlash() && item->isUserModified()) {
if (item->showStemSlash() && item->showStemSlash() != item->propertyDefault(Pid::SHOW_STEM_SLASH).toBool()) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As part of #28118 I've found myself doing kind of the opposite of this, i.e. override/specialize isUserModified as necessary to include this kind of information. In principle, I'd find it preferable for the read/write modules to know as little as possible about the inside working of each EngravingItem, so I think this kind of information would be better hidden inside the isUserModified method. But it's just a thing of principle so feel free to also do this in a next PR

@miiizen miiizen force-pushed the 27944-slash-save branch from 2c943f2 to 4cad96f Compare June 4, 2025 14:16
@miiizen miiizen merged commit 4e613ef into musescore:master Jun 4, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Grace notes after: slash through stem is not saved

2 participants