Skip to content
This repository has been archived by the owner on Aug 26, 2019. It is now read-only.
This repository has been archived by the owner on Aug 26, 2019. It is now read-only.

Custos bug #277

Open
zoemcl opened this issue Jan 19, 2018 · 0 comments
Open

Custos bug #277

zoemcl opened this issue Jan 19, 2018 · 0 comments
Assignees
@zoemcl
Labels
Bug Core Functionality Project: NEON

Comments

@zoemcl
Copy link
Contributor

zoemcl commented Jan 19, 2018

If there is more than one custos on a staffline, upon save, undo or refresh, all the elements will be pushed to before the first custos. We need to find a way to make sure the elements stay in their proper positions in these cases, perhaps making them dependant on the last custos instead of the first.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@zoemcl zoemcl

Labels
Bug Core Functionality Project: NEON
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vigliensoni @zoemcl