Fix #4795 Sensor Range Bands Not Showing Until Movement Begins. #4946
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
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.
Fixes #4795 - Whenever a unit is selected in the movement phase, the
MovementDisplay::selectEntity()call clears the sensor ranges. This fix removes the call to clear the sensor ranges when an entity is selected allowing the sensor range sprite to be drawn be default when the feature is enabled.Additionally, if a player would toggle off sensor ranges and then select a new entity, the ranges would be cleared due to the feature being toggled off - causing the sensors range to not display when the sensor range is toggled back on. (at least until some event triggers the re-calculation of the ranges.)