Bug #5925
Bug #5918 wrongly classed as "not a bug" because the tester can not read
Status:
Moot
Severity:
Unworthy
Assignee:
-
Category:
Bug Tracker
Target version:
-
Start date:
11/11/2015
% Done:
0%
Language:
English (US)
Mod Related:
No
Votes:
Description
Bug #5918 talks about pointing AT or AWAY from the target and DOES NOT mention prograde NOR retrograde to the target.
Related issues
History
#1 Updated by RexKramer about 9 years ago
- Status changed from New to Not a Bug
- % Done changed from 0 to 100
#2 Updated by RexKramer about 9 years ago
- Status changed from Not a Bug to Duplicate
#3 Updated by RexKramer about 9 years ago
- Related to Bug #5022: Target node deselects when stationary or close to 0.0m/s added
#4 Updated by RexKramer about 9 years ago
- Related to deleted (Bug #5022: Target node deselects when stationary or close to 0.0m/s)
#5 Updated by RexKramer about 9 years ago
- Is duplicate of Bug #5022: Target node deselects when stationary or close to 0.0m/s added
#6 Updated by RexKramer about 9 years ago
- Is duplicate of Bug #5316: SAS "target tracking" mode not available if zero speed relative to target added
#7 Updated by orcaman98 about 9 years ago
Comwarrior69 wrote:
Bug #5918 talks about pointing AT or AWAY from the target and DOES NOT mention prograde NOR retrograde to the target.
You did, between the pictures. Anyway, otherwise, you're right. There's no reason for target/anti-target to be greyed out, as the only way you could get wild behavior from that is if you passed through the target. Target-relative prograde and retrograde would be prone to such behavior, and I completely understand removing them, but bearing to target should remain an option.
#10 Updated by Squelch about 9 years ago
- Related to Bug #5918: SAS point at/away from target grayed at zero closing speed added
#11 Updated by Squelch about 9 years ago
- Status changed from Duplicate to Moot
- Severity changed from Critical to Unworthy