Fix problems caused by a revert in FPS entry change #503
Conversation
This file contains 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
|
You're fixing problems that you caused yourself with the major change you made yourself. Just change your settings file. |
|
Em...that has been released in a pre-release. Aren't we ensuring the compatibility in each pre-release? |
|
Nope. They're pre-releases. Or we can just delete it. |
|
Delete what? |
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.
A change in FPS entry made by #425 has been reverted by 9de1e2a, but the change has already been proposed in 2.2.0-dev3, which may cause potential compatibility problem, so this fixes this problem, also redoes a change by #457 and a change from interval of 1 to 10 in FPS setting values.