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

RenderOptions should distinguish overridden from transient values #135

Open
jacobtylerwalls opened this issue Sep 25, 2021 · 0 comments
Open

Comments

@jacobtylerwalls
Copy link
Member

This is where the renderOptions and some sort of a status marker are in conflict -- we are using "startNewSystem" to mean both "override layout to start new system" and also "in this render should I start a new system?"

Originally posted by @mscuthbert in #126 (comment)


We have overriddenWidth but nothing similar for the other render options, so when for instance, systemWidthsAndBreaks() sets left, width, displayClef, etc., we have only true/false values at our disposal, or possibly undefined, not a "never" or "always" or "overridden 400" etc.

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

No branches or pull requests

1 participant