Skip to content
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

fix #78416: Tempo text oddities in score with linked parts until save/reopen #2451

Closed
wants to merge 1 commit into from

Conversation

hpfmn
Copy link
Contributor

@hpfmn hpfmn commented Mar 15, 2016

always update tempo on tempotextchange and use _text instead of _layout

@hpfmn
Copy link
Contributor Author

hpfmn commented Mar 31, 2016

Some more explanation: the if statement just checked whether the tempotext object itself changed - but it didn't check if the tempo is a different one in the song!
Maybe it is better to have two conditions? like:

  • one for status of tempotext object
  • one for status of songtempo

Change from plaintext to xmltext is because plaintext uses _layout which doesn't get updated if the text gets set by the score itself (by method Text::setXmlText) - _layout just gets updated if someone types things into the text
Subpart's texts get updated automatically by updating the text in the main score - but this doesn't update _layout which contains than old data (most likely the default of 80) - which than changes the tempo to wrong values

score()->fixTicks();
score()->setPlaylistDirty();
}
setTempo(nt);
Copy link
Contributor

Choose a reason for hiding this comment

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

we could also just drop the local var nt althogether, as it is used only once.

@hpfmn hpfmn force-pushed the fix-78416 branch 2 times, most recently from 78a40cf to fd05878 Compare May 9, 2016 09:32
@Jojo-Schmitz
Copy link
Contributor

won't this PR collide with #2591 ?

@hpfmn
Copy link
Contributor Author

hpfmn commented May 17, 2016

yes it will collide - but which one gets merged first - I'll just edit the other one ;)

@IsaacWeiss
Copy link
Contributor

@lasconic, I may be not the only one to think that this was long since merged, but it seems it wasn't. Would you care to check on it?

@Jojo-Schmitz
Copy link
Contributor

Rebase needed

@Jojo-Schmitz
Copy link
Contributor

Not only a rebase is needed, it also doesn't seem to work (taking that code and resolving the merge conflicts)

@anatoly-os
Copy link
Contributor

The issue is seemed to be fixed by recent changes in tempo mapping.

@anatoly-os anatoly-os closed this May 21, 2019
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.

4 participants