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

re-connect of neighbour shape elements after adding stems or heads #358

Closed
Bacchushlg opened this issue Feb 21, 2020 · 3 comments
Closed

Comments

@Bacchushlg
Copy link
Collaborator

it happens from time to time that stems or heads are not recognized. No problem, they can be added manually rather quickly.
Unfortunately after adding them, some connections to neighbour elements are not refreshed as it is done in similar cases:

  • beams: after adding a stem to an existing beam (normally this happens for a stems that is in the middle of a beam) the stem is not connected to this beam, it must be connected explicitly)
  • lyrics: after adding a head, a lyrics element is not connected automatically

typical Example:
image

@hbitteur
Copy link
Contributor

Current policy is that links are searched at (manual) insertion time of symbol A only if A needs such link.
In the 2 cases mentioned here, the policy gives:

  • a stem does not need a beam.
  • a head chord does not need a lyric item.

@Bacchushlg
Copy link
Collaborator Author

I understand the current policy. But it would help editing, if this feature could be added.
A stem that ends at (or near) a beam is very likely part of the beam. After adding the stem, actually the rhythm is not correct, because the added note does not get the correct timing.
This finally leads to an incorrect output - sometimes with corrupt timing of the measure(s).

@hbitteur
Copy link
Contributor

hbitteur commented Nov 19, 2021

This already worked when inserting a stem near beams.

This now works also when inserting a compound note (head+stem): beam potential links are displayed when moving the compound and they are indeed created at drop time.
See commit a28c84b in development branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants