Allow curves to be tabled inline#6674
Merged
Merged
Conversation
Goober5000
reviewed
Apr 12, 2025
Goober5000
reviewed
May 22, 2025
Goober5000
reviewed
May 22, 2025
Goober5000
approved these changes
Jun 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This allows simple curves to be tabled inline wherever they are used, instead of forcing individual curve table entries.
Inline curves notably support only a much smaller subset of features, but that is perfectly sufficient for a large number of curves.
This can be used everywhere where curves are currently addressed by name in parsing.
An example table with inline curves would look as follows:
Note, that this will prevent curves from having a name that starts with an opening parenthesis.
For now, possible interpolations in inline mode are:
--: Linear,-|: Constant,-/: Square with ease-in,/-: Square with ease-out.