Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@HoneySkull
Copy link
Collaborator

This PR fixes a side-effect that was introduced in PR #5712 to resolve #5700.

The side-effect is: When in the movement phase with Visual and Sensor range enabled, when the selected unit has no movement path, or Escape, or Backspace were pressed, the Visual and Sensor Range sprites would be removed.

The correct operation is that the Visual and Sensor Range must be able to be toggled on and off independently of the Movement Envelope and Movement Modifier sprites.

@codecov
Copy link

codecov bot commented Jul 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.09%. Comparing base (ef98c2a) to head (3fe0386).
Report is 39 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #5726      +/-   ##
============================================
- Coverage     29.29%   29.09%   -0.20%     
- Complexity    13877    13879       +2     
============================================
  Files          2468     2505      +37     
  Lines        264115   265930    +1815     
  Branches      47316    47556     +240     
============================================
+ Hits          77368    77378      +10     
- Misses       182845   184653    +1808     
+ Partials       3902     3899       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@HoneySkull HoneySkull merged commit 6cad801 into MegaMek:master Jul 11, 2024
@HoneySkull HoneySkull deleted the fix_visual_sensor_range branch September 19, 2024 04:43
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

Successfully merging this pull request may close these issues.

[49.20] "Show best possible modifiers" overlay not removed on pressing Escape

2 participants